CrunchJunkie

research_keywords

Look up keywords around a seed in DataForSEO Labs (Google, one country and language) for a client: contains (keywords with the seed's words), ideas (same topic), related (searched together) or questions. A lookup stored in the last 30 days answers at no cost and without a preview. Otherwise it costs money on the workspace's own DataForSEO account or its Rank Tracker budget: the preview states the most it can cost and the budget left. Requires write actions and "Allow actions that spend AI", and counts toward the 20 assistant-started spend actions per workspace per day. Returns the key and the first rows; get_keyword_research filters the rest. Keywords are tracked with add_rank_keywords (Google positions) or turned into AI tracking prompts with suggest_prompts (keywords) and add_tracking_prompt.

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": {
      "clientId": "<clientId>",
      "seed": "<seed>",
      "country": "<country>",
      "language": "<language>"
    },
    "name": "research_keywords"
  }
}

Input Schema

Name	Required	Description
`mode`	No	Default contains.
`seed`	Yes	The seed keyword, up to 10 words.
`limit`	No	Keywords to fetch (default 300); the price grows with it.
`confirm`	No	Set true to run. Omit for a preview with the cost. With confirm:true, also pass the preview's previewToken.
`country`	Yes	ISO 3166-1 alpha-2.
`clientId`	Yes	Client id (from list_clients); its joins are read and the lookup is filed under it.
`language`	Yes	Language code: one keyword research offers for that country (languagesByCountry in get_keyword_research_setup; Spain is Spanish only).
`previewToken`	No	With confirm:true: the previewToken from this tool's preview (valid 15 minutes, once, for exactly the previewed arguments).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

changedInput schema / properties / language / description

Previous value: -"Language code (get_keyword_research_setup lists them)."New value: +"Language code: one keyword research offers for that country (languagesByCountry in get_keyword_research_setup; Spain is Spanish only)."

AddedNov 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well past readOnlyHint=false and destructiveHint=false: it discloses that calls cost money on the workspace's own DataForSEO account or Rank Tracker budget, that a preview states the maximum cost and remaining budget, that write actions and 'Allow actions that spend AI' are required, and that there is a cap of 20 assistant-started spend actions per workspace per day.

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 the lookup and its modes, then cost mechanics, then return shape, then follow-on tools — a sensible order. It is a dense single paragraph with several clauses per sentence, which costs some readability against the information it carries.

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 an 8-parameter tool with no output schema that mutates state and spends money, the description covers the preview/confirm flow, billing source, permission prerequisites, rate cap, and the return shape ('the key and the first rows'). Nothing an agent needs to call it safely is missing.

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

Parameters4/5

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

Schema coverage is 100%, so most parameter meaning is already documented; the description still adds the confirm/previewToken protocol, the fact that price grows with limit, and the constraint that language must be one offered for that country.

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 — 'Look up keywords around a seed in DataForSEO Labs (Google, one country and language)' — and enumerates the four modes (contains/ideas/related/questions), which is what actually differentiates it from siblings like lookup_keyword_volumes or get_keyword_research.

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?

Gives the when-to-use condition (per-client keyword discovery), the when-free path (a lookup stored in the last 30 days answers at no cost and without preview), and explicitly routes downstream work to add_rank_keywords and suggest_prompts plus result paging to get_keyword_research.

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

All CrunchJunkie 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?