Skip to main content
Glama

Visibility Genies

Read saved keyword volume history

get_saved_keyword_volume_history
Read-only

Reads monthly Google search volume history already bought for exactly this list of keywords in this project, however old, for free. It never buys: a list not saved is named with the price get_keyword_volume_history would pay.

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_saved_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.

Output Schema

NameRequiredDescriptionDefault
metaNo
boughtYes
savedAtYes
keywordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: history is free, however old, and it never purchases; unsaved lists return a price reference instead. It does not discuss auth or rate limits, but those are less critical here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core read behavior and immediately followed by the key non-purchase constraint. There is no redundant or filler wording.

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?

Given the rich schema, annotations, and output schema, the description supplies the remaining decision-critical context: saved-only scope, free access, and the fallback pricing behavior for unsaved lists. Nothing essential for correct tool selection appears missing.

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 the input schema already documents projectId, keywords, languageCode, and locationCode thoroughly. The description reinforces that the keyword list must be exactly the saved list in the project, but adds no syntax or format details beyond the schema.

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?

The description states a specific verb and resource: it reads monthly Google search volume history for saved keywords in a project. It also distinguishes itself from get_keyword_volume_history by saying it never buys and that unsaved lists are priced by that sibling.

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?

It clearly frames the tool as the free read path for keywords already bought/saved, and explicitly names get_keyword_volume_history as the alternative when a list is not saved. The when-to-use condition is therefore explicit rather than inferred.

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