Provided by DataForSEO
Identify the search intent of Google keywords with DataForSEO
Look up whether each keyword in a list is informational, navigational, commercial or transactional, for one language. One row per keyword supplied, carrying its most likely intent label with a probability and any secondary intents. The keywords and a language are the whole input. One request per call, priced by the vendor's own rate card; an empty result set is reported as no result.
How to run it
Step 1Set up
Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.
set up https://glasser.ai/SKILL.md
Show me how to use the DataForSEO endpoint /v3/dataforseo_labs/google/search_intent/live on Glasser.glasser run -p dataforseo -e '/v3/dataforseo_labs/google/search_intent/live' -i '{"keywords":["login page","audi a7","elon musk","milk store new york"],"language_code":"en"}' --endpoint-version 2Uses endpoint version 2. Inspect the current price before running. Install and log in first on Get Started.
Once per Run:
IDEMPOTENCY_KEY=$(uuidgen)Run it, and copy this same block to send it again:
curl -X POST https://api.glasser.ai/v1/runs \
-H "Authorization: Bearer gl_..." \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"dataforseo","endpoint":"/v3/dataforseo_labs/google/search_intent/live","input":{"keywords":["login page","audi a7","elon musk","milk store new york"],"language_code":"en"},"endpoint_version":2}'Reuse the same Idempotency-Key to send it again: the second send is a read of the first Run. A new key is a new Run and a new Charge. Uses endpoint version 2; inspect the current price before running.
Step 2Try a specific example task
When you need to plan new content, you might organize keyword ideas into related topics to build a workable content plan.
Copy this prompt into your agent to group keyword ideas for your content plan.
Use dataforseo:/v3/dataforseo_labs/google/search_intent/live on Glasser.
Group the returned keywords into topics I can use to plan content.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"keywords",
"language_code"
],
"properties": {
"tag": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"keywords": {
"type": "array",
"items": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"maxItems": 100,
"minItems": 1
},
"language_code": {
"type": "string",
"maxLength": 2048,
"minLength": 1
}
},
"additionalProperties": false
}{
"keywords": [
"login page",
"audi a7",
"elon musk",
"milk store new york"
],
"language_code": "en"
}This Endpoint publishes no output schema. You get the Provider's own response body, unchanged — we do not warrant a shape we cannot guarantee.
How pricing works
| Base fee | The same price with or without matching data. | $0.012 |
|---|---|---|
| Per row | For each row returned. | $0.00012 |
| Maximum per Run | The total charge will not exceed this amount. | $0.024 |
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The Run exceeded its time limit. | $0.00 |
| Internal failure | An internal error prevented completion. | $0.00 |