Skip to main content
Glama

Keyword Search Volume & CPC

keyword_data
Read-onlyIdempotent

Return search-volume, CPC, and competition data for a keyword.

Related: keywords_trends.

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_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoMarket. Default: US-EN
keywordYesKeyword to research

Output Schema

NameRequiredDescriptionDefault
errorNoError message when success is false
keywordNo
low_cpcNoLow range cost-per-click in USD
successNo
high_cpcNoHigh range cost-per-click in USD
competitionNoCompetition index (0 to 1)
search_volumeNoAverage monthly search volume
competition_levelNoLOW, MEDIUM, or HIGH

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Changed1 schema field changed
    • changedOutput schema / properties / search_volume / description
      Previous value: -"Average monthly search volume on Google"New value: +"Average monthly search volume"
  3. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered without the description. The description adds nothing beyond that — no data freshness, market coverage, or rate-limit context — but it also contradicts nothing.

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 short sentences with the core purpose front-loaded and no filler. The trailing 'Related: keywords_trends' fragment is terse to the point of being uninformative, but it costs almost nothing.

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?

For a simple two-parameter lookup with a rich annotation set and an output schema, the description covers the essential purpose. Minor gaps remain around what 'competition' means and how CPC is denominated across markets, but nothing blocks a correct call.

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% and the country enum with its US-EN default plus the keyword field are fully documented in the schema itself. The description adds no extra meaning about parameter effects, so the 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?

The description names a specific verb ('Return') and concrete resources (search-volume, CPC, competition data for a keyword), which is materially more specific than the title alone. It does not differentiate itself from siblings beyond a vague 'Related: keywords_trends' pointer, so an agent still can't tell from this text alone when this tool beats the sibling.

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?

'Related: keywords_trends' signals an adjacent tool exists but gives no condition for choosing one over the other, and there is no when-to-use or when-not-to-use guidance. Usage is only inferable from the tool name and purpose sentence.

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.