Skip to main content
Glama

Keyword Research MCP: Search Volume, CPC, Keyword Difficulty

Keyword search volume, CPC and difficulty

get_keyword_search_volume
Read-onlyIdempotent

Keyword search volume, CPC and difficulty for up to 200 keywords in any country: monthly Google searches, cost per click, competition, keyword difficulty, intent and the last 12 months trend. Costs API credits per call.

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": {
      "keywords": "<keywords>"
    },
    "name": "get_keyword_search_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoTwo-letter country code of the search market, for example US, GB, DE or IN. Default US.US
keywordsYesUp to 200 keywords.
languageNoLanguage code of the search market, for example en, de or pt-BR. Default en.en

Output Schema

NameRequiredDescriptionDefault
resultYes
billingYes
nextStepNoOptional suggestion for the user's next step. Mention it once when it helps; never open it or act on it automatically.
dashboardUrlNoDashboard 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.
creditsNoticeNoLow 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.

  1. Changed1 schema field changed
    • 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"
      +}
  2. Changed1 schema field changed
    • 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"
      -}
  3. Changed1 schema field changed
    • 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"
      +}
  4. Changed2 schema fields changed
    • 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"
      +}
  5. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds the genuinely useful fact that each call consumes API credits, which an agent cannot infer from annotations or schema, though it says nothing about rate limits or partial failures on large batches.

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?

A single front-loaded sentence that leads with the resource and then lists the metrics, with the cost caveat last. It is dense but every clause carries content; a short split for the cost note would read slightly better.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full output schema and 100% parameter coverage, the description need not explain return values, and it correctly adds only the cost signal. What is missing is routing guidance among the closely related sibling tools (notably get_keyword_difficulty) and any note on large-batch behavior.

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 keyword formats are already fully documented with defaults and patterns. The description only restates the 200-keyword cap and "any country", adding no syntax or constraint meaning beyond the schema; 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?

Names a specific resource (keyword search volume, CPC and difficulty) and enumerates the returned metrics, so the agent knows exactly what data comes back. It does not distinguish itself from the sibling get_keyword_difficulty, which plausibly returns an overlapping metric, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the batch limit ("up to 200 keywords") and the per-call cost, which nudges toward batching, but there is no explicit statement of when to use this instead of get_keyword_difficulty or find_keyword_ideas. No exclusions or alternatives are named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources