Provided by DataForSEO
Review demographic interest in selected keywords with DataForSEO
Hand over up to 5 keywords and one location and read, for each keyword, how its popularity splits across age bands and between female and male searchers, plus a comparison of the keywords within each age band and gender, as DataForSEO Trends measures it. Optional web, news or shopping search type and a date range or time range. 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/keywords_data/dataforseo_trends/demography/live on Glasser.glasser run -p dataforseo -e '/v3/keywords_data/dataforseo_trends/demography/live' -i '{"keywords":["rugby","cricket"],"location_code":2840}' --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/keywords_data/dataforseo_trends/demography/live","input":{"keywords":["rugby","cricket"],"location_code":2840},"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/keywords_data/dataforseo_trends/demography/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"
],
"properties": {
"tag": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"type": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"date_to": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"keywords": {
"type": "array",
"items": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"maxItems": 5,
"minItems": 1
},
"date_from": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"time_range": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"location_code": {
"type": "integer"
},
"location_name": {
"type": "string"
}
},
"additionalProperties": false
}{
"keywords": [
"rugby",
"cricket"
],
"location_code": 2840
}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
| Data returned or no match | The same price with or without matching data. | $0.0024 |
|---|---|---|
| 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 |