Skip to main content
Glama

Visibility Genies

Get keyword volume history

get_keyword_volume_history

Buys monthly Google search volume since 2021 for up to 100 keywords in one market: several years of demand, beyond the 12 months research shows. Estimated price: up to $0.03 for one keyword, up to $0.05 for 100, one request billed per keyword returned; keywords Google has no data for are free. The same list bought in the last 30 days is read free, and every purchase opens free on Keyword Research's Volume history view; get_saved_keyword_volume_history reads it without buying. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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

Input Schema

NameRequiredDescriptionDefault
keywordsYes1 to 100 keywords, e.g. ['ski boots', 'ski jackets'].
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
languageCodeNoLanguage code such as en, es or vi. When left out, the language of the project's default market is used (see list_projects).
locationCodeNoMarket location code, for example 2840 for the United States. When left out, the project's default market is used (shown by list_projects and changed in project settings). A few countries, Iceland (2352) among them, only have Google Ads data: search volume, CPC and trends are available there, but keyword difficulty, search intent and domain analytics are not.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
boughtYes
savedAtYes
keywordsYes
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=true; the description goes far beyond with per-keyword billing, estimated prices, free keywords with no data, the 30-day free re-read, spend-limit pre-authorization, and the refusal-before-purchase behavior. That is exactly the cost/auth context an agent needs before invoking a paid call.

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?

Dense and front-loaded with the capability first, then pricing, then the free-read alternative, then the spend-limit safety flow. Some sentences are long and stacked with clauses (billing, hold, charge, refusal) that could be split, but nothing is redundant.

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 a high-complexity, money-spending tool this covers cost, limits, alternatives, and the refusal/approval loop, while return values are handled by the existing output schema. An agent has enough to decide and to call correctly without guessing.

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?

With 100% schema coverage the baseline is 3, but the description adds real meaning about approvedMaxCostUsd: it is only needed after a refusal, must be set to the amount the user approved, and must never be set without asking. It also contextualizes that the per-keyword charge scales with the keywords parameter, which the schema does not say.

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?

Opens with a specific verb and resource: 'Buys monthly Google search volume since 2021 for up to 100 keywords in one market'. The scope and the 12-month research contrast make it immediately distinguishable from the sibling get_saved_keyword_volume_history, which is named later.

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?

Explicitly states when this tool is needed versus the free read path: the same list bought in the last 30 days is free, and get_saved_keyword_volume_history reads purchased history without buying. It also gives the escalation procedure for refused calls (ask the user, then retry with approvedMaxCostUsd).

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