Agent Data API

ranked_keywords

Idempotent

Up to 25 Google keywords a domain ranks for, with position, ranking page, search volume, CPC and difficulty (DataForSEO Labs Ranked Keywords). Returns: JSON with target, total_available, keywords. PAID: 0.04 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": {
      "domain": "<domain>"
    },
    "name": "ranked_keywords"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes	Domain to analyze, e.g. example.com. A pasted URL is reduced to its domain; IP addresses and ports are rejected.
`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

A3.9/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing cost (0.04 USDC), chain/asset (eip155:8453), payment mechanism (_meta["x402/payment"], x402 v2), a concrete client library, and the precise failure mode ('payment required' result with no charge). Annotations only cover readOnly/openWorld/idempotent, so this cost-and-payment disclosure is substantive added context.

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-loaded with purpose and return shape, then payment requirements, then failure behavior. Dense but almost every sentence carries information; the pricing/protocol sentence is long but earns its place given the paid nature of the tool.

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?

With no output schema, the description supplies the return keys (target, total_available, keywords), the 25-item cap, and the payment/error path, which is enough to invoke and interpret results. Minor gap: no mention of pagination or how to retrieve beyond the first 25 results even though total_available is returned.

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%, with domain normalization rules, language defaults and location code examples already documented in the schema. The description adds only the 'up to 25' result cap and the return JSON keys, not new parameter meaning, so baseline 3 applies.

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+resource: 'Up to 25 Google keywords a domain ranks for' with the exact metric set (position, ranking page, search volume, CPC, difficulty) and names the data source (DataForSEO Labs Ranked Keywords). It does not explicitly differentiate itself from close siblings like keywords_for_site, keyword_metrics or domain_overview, which is the only thing keeping it from a 5.

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 description gives a clear precondition (must be called from an x402-capable MCP client that attaches payment in _meta["x402/payment"]) and states what happens without payment. However, it never says when to choose this over alternatives such as keywords_for_site or keyword_metrics, so tool selection is left implicit.

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?