Agent Data API

google_trends

Idempotent

Google Trends interest over time (past 12 months, relative 0-100) for up to 5 keywords compared against each other (DataForSEO Google Trends Explore Live). Returns: JSON with keywords, points. PAID: 0.025 USDC per call (USDC on eip155:8453, x402 v2). Requires an x402-capable MCP client that attaches the payment in _meta["x402/payment"] (e.g. createx402MCPClient from @x402/mcp). Without a payment this tool returns a "payment required" result and charges nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keywords": "<keywords>"
    },
    "name": "google_trends"
  }
}

Input Schema

Name	Required	Description
`keywords`	Yes	Keywords to look up: 1 to 5 entries, each up to 80 characters / 10 words. Lowercased, duplicates removed.
`language_code`	No	Language code such as en or de. Default: English if available for the country, else its first language. Unsupported country/language pairs are refused before payment.
`location_code`	No	DataForSEO location code. Country level: 2840 = United States (default), 2276 = Germany, 2040 = Austria, 2756 = Switzerland. Google SERP, Maps, News, Images and Local Market Check also accept city/region codes in Germany, Austria and Switzerland (free lookup: GET /api/v1/locations?q=...).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

changedInput schema / properties / location_code / description

Previous value: -"DataForSEO country code. 2840 = United States (default), 2276 = Germany, 2826 = United Kingdom. Country-level codes only."New value: +"DataForSEO location code. Country level: 2840 = United States (default), 2276 = Germany, 2040 = Austria, 2756 = Switzerland. Google SERP, Maps, News, Images and Local Market Check also accept city/region codes in Germany, Austria and Switzerland (free lookup: GET /api/v1/locations?q=...)."

AddedOct 22, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing the paid cost (0.025 USDC on eip155:8453, x402 v2), the payment transport, the upstream provider (DataForSEO Google Trends Explore Live), and the non-charging failure mode. The readOnlyHint=false flag is not explained (the write-like trait is presumably billing), and rate limits/timeouts are not covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Opens with what the tool returns, then the paid/payment mechanics, then the no-payment fallback — front-loaded and ordered by decision importance. Every sentence carries information an agent needs before calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter tool with no output schema, the description covers cost, payment, scope, and return shape ('JSON with keywords, points'). The one soft spot is that 'points' is not explained (whether they carry timestamps/date labels), leaving the return structure partly opaque.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, and the description still adds meaning: keywords are compared against each other rather than queried individually, and values are relative 0-100 over a fixed 12-month window, which the schema does not say. That is real semantic value on top of a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Google Trends interest over time'), the metric scale (relative 0-100), the time window (past 12 months) and the cardinality limit (up to 5 keywords compared). It never names a sibling alternative such as keyword_metrics or ai_keyword_demand, so differentiation is left to the agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear preconditions for use: an x402-capable MCP client that attaches payment in _meta["x402/payment"], and states the outcome when the precondition fails ('payment required' result, no charge). It does not say when to prefer this tool over sibling keyword/demand tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Data API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?