Keyword Research MCP: Search Volume, CPC, Keyword Difficulty

Keyword difficulty

get_keyword_difficulty

Read-onlyIdempotent

Keyword difficulty: how hard it is to rank organically in Google for up to 500 keywords, scored 0 to 100. Costs API credits per call.

Input Schema

Name	Required	Description	Default
`country`	No	Two-letter country code of the search market, for example US, GB, DE or IN. Default US.	US
`keywords`	Yes	Up to 500 keywords.
`language`	No	Language code of the search market, for example en, de or pt-BR. Default en.	en

Output Schema

Name	Required	Description
`result`	Yes
`billing`	Yes
`nextStep`	No	Optional suggestion for the user's next step. Mention it once when it helps; never open it or act on it automatically.
`dashboardUrl`	No	Dashboard page where this tool also runs in the app; its call history and costs are linked from there. Share it when the user asks what they ran or spent.
`creditsNotice`	No	Low API credit balance: tell the user once, with this link to add credits. Never open it automatically.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

addedOutput schema / properties / creditsNotice

Added value: +{
+  "additionalProperties": false,
+  "description": "Low API credit balance: tell the user once, with this link to add credits. Never open it automatically.",
+  "properties": {
+    "label": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "label",
+    "url"
+  ],
+  "type": "object"
+}

Changed1 schema field changedNov 3, 2026

removedOutput schema / properties / creditsNotice

Removed value: -{
-  "additionalProperties": false,
-  "description": "Low API credit balance: tell the user once, with this link to add credits. Never open it automatically.",
-  "properties": {
-    "label": {
-      "type": "string"
-    },
-    "url": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "label",
-    "url"
-  ],
-  "type": "object"
-}

Changed1 schema field changedNov 3, 2026

addedOutput schema / properties / creditsNotice

Added value: +{
+  "additionalProperties": false,
+  "description": "Low API credit balance: tell the user once, with this link to add credits. Never open it automatically.",
+  "properties": {
+    "label": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "label",
+    "url"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedOct 30, 2026

changedOutput schema / properties / dashboardUrl / description

Previous value: -"Dashboard page with this server's call history and costs. Share it when the user asks what they ran or spent."New value: +"Dashboard page where this tool also runs in the app; its call history and costs are linked from there. Share it when the user asks what they ran or spent."

addedOutput schema / properties / nextStep

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional suggestion for the user's next step. Mention it once when it helps; never open it or act on it automatically.",
+  "properties": {
+    "label": {
+      "description": "Short suggestion to show the user.",
+      "type": "string"
+    },
+    "url": {
+      "description": "Page in the user's CrakSEO account.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "label",
+    "url"
+  ],
+  "type": "object"
+}

First observedOct 28, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description goes beyond them by disclosing that each call consumes API credits and by bounding batch size and score range, which materially affects how an agent should budget calls.

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?

Two compact sentences, front-loaded with the metric definition, and the cost warning is placed where it will be read. Minor redundancy in repeating the 500-keyword limit already enforced by the schema.

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?

An output schema exists so return values need no explanation, and the description covers what the metric is, its scale, batch limits and cost. Only the absence of any routing guidance to sibling tools keeps it from being fully complete.

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 country, language and the keyword array are already fully documented in the schema. The description adds nothing about parameter semantics beyond restating the 500-keyword cap, 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 metric ('keyword difficulty'), its meaning ('how hard it is to rank organically in Google'), its scale (0-100), and its batch capacity (up to 500 keywords). An agent can immediately tell this is the difficulty-metric tool rather than a volume or ideas tool, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to reach for this tool versus get_keyword_search_volume, find_keyword_ideas, or find_competitor_keywords, and no stated prerequisites or exclusions. Usage is only inferable from the metric name itself.

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

All Keyword Research MCP: Search Volume, CPC, Keyword Difficulty 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?