Agent Data API

keywords_for_site

Idempotent

Up to 25 Google keywords relevant to a website, with search volume, CPC, competition, difficulty and intent (DataForSEO Labs Keywords For Site). Use it to find what a site should target; use ranked_keywords for what it already ranks for. Returns: JSON with domain, 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": "keywords_for_site"
  }
}

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

A4.4/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 nature (0.04 USDC, eip155:8453, x402 v2), the exact payment mechanism (_meta["x402/payment"]), and the failure mode when unpaid ('payment required', no charge). The annotations already cover safety (readOnly=false, destructive=false, idempotent=true), so the remaining gap is minor – it doesn't say whether results are cached or how billing failures mid-request are handled.

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 purpose, then the sibling contrast, then returns, then the payment block – a sensible order with little waste. The payment section is dense with identifiers but each detail is operationally necessary for a paid tool.

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

Completeness5/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 still names the return shape (domain, total_available, keywords), and it fully documents the payment handshake and no-charge fallback. An agent has everything needed to call it and to predict both success and failure outcomes.

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% and the schema already explains domain normalization, language defaults, and location codes in detail. The description adds no parameter-level guidance beyond implying a website/domain input, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Up to 25 Google keywords relevant to a website') plus the exact data fields returned, and names the data source (DataForSEO Labs Keywords For Site). It explicitly distinguishes itself from the sibling ranked_keywords by contrasting 'what a site should target' with 'what it already ranks for.'

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

Usage Guidelines5/5

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

Names the alternative tool (ranked_keywords) and the exact condition that selects between them, so an agent can route without inspecting schemas. It also states the practical precondition for invocation: an x402-capable client with payment attached, otherwise nothing is charged.

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?