Agent Data API

keyword_gap

Idempotent

Keywords a competitor ranks for in Google but your domain does not: up to 25, highest search volume first, with the competitor's ranking page (DataForSEO Labs Domain Intersection). Returns: JSON with domain, competitor, total_available, keywords. PAID: 0.045 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>",
      "competitor": "<competitor>"
    },
    "name": "keyword_gap"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes	Your domain, e.g. example.com: keywords it already ranks for are excluded.
`competitor`	Yes	The competitor's domain, e.g. competitor.com: the keywords it ranks for are returned.
`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.

Changed2 schema fields changedOct 23, 2026

changedInput schema / properties / competitor / description

Previous value: -"Domain to analyze, e.g. example.com. A pasted URL is reduced to its domain; IP addresses and ports are rejected."New value: +"The competitor's domain, e.g. competitor.com: the keywords it ranks for are returned."

changedInput schema / properties / domain / description

Previous value: -"Domain to analyze, e.g. example.com. A pasted URL is reduced to its domain; IP addresses and ports are rejected."New value: +"Your domain, e.g. example.com: keywords it already ranks for are excluded."

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.5/5.0

Behavior5/5

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

Beyond the annotations, it discloses critical behavior: the tool is paid, costs 0.045 USDC per call, requires an x402-capable client with payment in _meta['x402/payment'], and returns a payment-required result without charging if no payment is attached. It also states the result cap and ordering, which materially affects how an agent should use the tool.

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?

The description is front-loaded with the core purpose, followed by result limits, return shape, and payment requirements. Every sentence contributes useful information, especially the payment/auth details that an agent must know before invoking the 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?

For a paid, read-only-style data query with no output schema, the description supplies the return JSON fields, payment prerequisites, failure behavior, and result constraints. Combined with full schema parameter descriptions, an agent has enough information to call it correctly.

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 the schema already documents all four parameters thoroughly, including domain, competitor, language_code, and location_code. The description adds little parameter-specific meaning beyond clarifying the overall gap logic, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource: keywords a competitor ranks for in Google but your domain does not. It distinguishes this from sibling keyword tools by naming the exact gap-analysis condition and the underlying DataForSEO Labs Domain Intersection source.

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?

The description makes the use case explicit: compare a domain against a competitor to find keywords the competitor ranks for but the domain does not. It does not explicitly name alternatives such as ranked_keywords or keywords_for_site, so it falls just short of full when-to-use/when-not guidance.

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?