Provided by DataForSEO
Analyze sentiment in content matching a keyword with DataForSEO
Read how the pages that mention one keyword, phrase or brand feel about it, across DataForSEO's index of crawled page text. The sentiments are split by polarity (positive, negative or neutral) and again by emotion (such as anger or happiness), and each split carries its own block of totals: how many pages, their combined rank, the domains behind them, and counts by page type, country and language. 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/content_analysis/sentiment_analysis/live on Glasser.glasser run -p dataforseo -e '/v3/content_analysis/sentiment_analysis/live' -i '{"keyword":"logitech"}' --endpoint-version 1Uses endpoint version 1. 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/content_analysis/sentiment_analysis/live","input":{"keyword":"logitech"},"endpoint_version":1}'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 1; 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/content_analysis/sentiment_analysis/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": [
"keyword"
],
"properties": {
"tag": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"keyword": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"page_type": {
"type": "array",
"items": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"maxItems": 100,
"minItems": 1
},
"rank_scale": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"internal_list_limit": {
"type": "integer"
},
"positive_connotation_threshold": {
"anyOf": [
{
"type": "number"
},
{
"enum": [
"Infinity",
"-Infinity",
"NaN"
],
"type": "string"
}
]
},
"sentiments_connotation_threshold": {
"anyOf": [
{
"type": "number"
},
{
"enum": [
"Infinity",
"-Infinity",
"NaN"
],
"type": "string"
}
]
}
},
"additionalProperties": false
}{
"keyword": "logitech"
}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.024036 |
|---|---|---|
| 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 |