Agent Data API

keyword_metrics

Idempotent

Google Ads search volume, competition, CPC and 12-month history for up to 1000 keywords per call (DataForSEO Google Ads Search Volume Live). Returns: JSON with keywords. PAID: 0.12 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": "keyword_metrics"
  }
}

Input Schema

Name	Required	Description
`keywords`	Yes	Keywords to look up: 1 to 1000 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=...)."

First observedOct 22, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Goes well past the annotations by disclosing price (0.12 USDC), the payment rail (eip155:8453, x402 v2), the required client capability and the exact _meta field, and the failure mode (returns 'payment required', charges nothing). This is the information an agent needs before invoking a paid, non-readOnly tool.

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

Conciseness4/5

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

Front-loads the capability and keeps the payment block compact; every sentence carries information. The 'Returns: JSON with keywords' fragment is vague filler but the rest is tight.

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?

Given a 3-parameter tool with no output schema, the description covers cost, auth prerequisites, and failure behavior well. The return payload is only sketched as 'JSON with keywords', so an agent still cannot anticipate the response shape, which keeps it short of a 5.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters are already fully documented, including location code examples and language defaulting. The description restates the 1000-keyword cap but adds no parameter semantics beyond the schema, which is the expected baseline here.

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?

Names the concrete resource and metric set: Google Ads search volume, competition, CPC and 12-month history, plus the backing source (DataForSEO Google Ads Search Volume Live). It is clearly distinguishable from siblings like google_serp or keyword_ideas by the metrics returned, though it does not name any sibling explicitly.

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

Usage Guidelines3/5

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

The batch framing ('up to 1000 keywords per call') implies when this tool is a good fit, but there is no explicit when-to-use / when-not-to-use guidance against keyword_difficulty, ai_keyword_demand, or keyword_ideas. Usage must be inferred from the metric list.

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?