Skip to main content
Glama

SEO and Keyword Data API

Monthly search volume history (up to 20 keywords)

keyword_volume_history
Read-onlyIdempotent

Monthly Google search volume history for up to 20 keywords in one $0.048 call: every month the data has (typically several years), oldest first, plus current volume, CPC and competition (Google Ads data). Use when you need seasonality or long-term demand trends. Over 20 keywords is a free 400. Keywords without data are listed in missing (still charged). Bad input is free; upstream errors are not charged. Price: $0.048 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": {
      "keywords": "<keywords>"
    },
    "name": "keyword_volume_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoOptional ISO 3166-1 alpha-2 code or country name, used when locationCode is absent (uk = gb).
keywordsYesKeywords to look up (1-20; each at most 80 characters, normalised to lower case; one that is then empty, over 10 words or over 80 characters is listed in missing).
languageCodeNoLanguage 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.
locationCodeNoGoogle 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.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only cover safety (readOnly/ idempotent /openWorld), so the description carries real weight and does: pricing per successful call, billing edge cases (missing-data keywords still charged, bad input free, upstream errors not charged), and the payment mechanism via _meta['x402/payment']. That is precisely the operational context an agent needs before spending money.

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 resource and the time-series shape, then usage, then cost. Every sentence carries information, though the telegraphic phrasing ('Over 20 keywords is a free 400', 'Bad input is free') makes the billing rules slightly harder to parse than they need to be.

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?

No output schema exists, so the description supplies the return shape itself: a month-by-month series oldest-first, current volume/CPC/competition, and a missing list for keywords without data. Combined with pricing and payment mechanics, an agent can call this correctly without further inference.

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, locationCode, languageCode and the keyword normalization rules are already fully documented in the schema. The description adds only the 'missing' list semantics and the 20-keyword 400 behavior, which is marginal gain over structured data.

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 verb and resource ('Monthly Google search volume history for up to 20 keywords') and pins down the payload: every month available, oldest first, plus current volume, CPC and competition. This clearly separates it from current-volume siblings like keyword_search_volume, though it never names an alternative explicitly.

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?

Gives a concrete selection cue: 'Use when you need seasonality or long-term demand trends.' It also sets a hard boundary ('Over 20 keywords is a free 400'), so an agent knows when to split inputs. It stops short of naming the sibling to use instead when only current volume is wanted.

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.