SEO and Keyword Data API

Keyword variations containing a phrase (up to 100)

keyword_variations

Read-onlyIdempotent

Keyword variations: long-tail Google searches that contain a seed phrase, each with search volume, CPC, competition, keyword difficulty and search intent; up to 100 in one $0.04 call (Google Ads data). Use when you need phrase-match ideas for a keyword, sorted by volume. No matches returns empty results (still charged). Bad input is free; upstream errors are not charged. Price: $0.04 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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": {
      "keyword": "<keyword>"
    },
    "name": "keyword_variations"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum variations to return (1-100). Defaults to 20.
`country`	No	Optional ISO 3166-1 alpha-2 code or country name, used when locationCode is absent (uk = gb).
`keyword`	Yes	Seed phrase; every result contains it (at most 80 characters; normalised like keyword-ideas).
`languageCode`	No	Language code (2-letter). Defaults to en. An unsupported location falls back to 2840 (United States) with en (or the requested language if the United States offers it); a supported location with a language it does not offer uses that location's default language (en if offered). Either way market.fallback is true and market.warnings says what was used.
`locationCode`	No	Google Ads location code (geo target ID). Defaults to 2840 (United States); an unsupported code falls back to 2840 (United States, market.fallback).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

AddedNov 3, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only cover read-only/open-world/idempotent, but the description discloses the costly behaviors an agent must know: empty results on no matches are still billed, bad input is free, upstream errors are not charged, and the exact $0.04 per-call price with the x402 USDC-on-Base payment passed in _meta["x402/payment"]. That is payment/auth context the annotations cannot supply.

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 what the tool returns and its differentiator, then usage, then billing caveats — a sensible order. Slightly redundant on price (mentioned as 'one $0.04 call' and again as an explicit 'Price:' clause), but nearly every sentence carries decision-relevant information.

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 enumerates the returned metrics (volume, CPC, competition, difficulty, intent), the 100-result ceiling, and the empty-result case. Billing and payment mechanics are spelled out, so an agent has everything needed to call it correctly and understand the cost.

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%, including limit range, locationCode fallback to 2840, and the country/locationCode precedence, so the schema already carries parameter meaning. The description adds only the 100-cap and volume ordering, which is marginal beyond what the schema states — baseline 3.

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 concrete resource and its defining constraint: long-tail Google searches that contain a seed phrase, returning volume, CPC, competition, difficulty and intent. That 'every result contains the seed' rule genuinely separates it from broader idea tools like keyword_ideas or related_keywords, though no sibling is named explicitly in the description text.

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?

'Use when you need phrase-match ideas for a keyword, sorted by volume' gives a clear selection condition. It stops short of exclusions — it never says when to prefer keyword_ideas, related_keywords, or keyword_overview instead, leaving the agent to infer the boundary from the 40+ siblings.

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

All SEO and Keyword 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.