Skip to main content
Glama

Visibility Genies

Get search results history

get_serp_history

Google's results for a keyword as the data service saved them during one past month: each snapshot's date, the SERP features on the page and its top 20 organic results with position, domain, URL and title. Shows who ranked where before, to see whether rankings moved. The data service keeps the last 12 months. Estimated price: up to $0.01, one request for a month's snapshots. A month saved within 30 days is read free, and it opens free in Keyword Research's SERP view. 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>",
      "keyword": "<keyword>",
      "month": "<month>"
    },
    "name": "get_serp_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYesThe month as 'yyyy-mm', one of the last 12 months, this one included.
keywordYesThe keyword.
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
boughtNo
snapshotsNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only give readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the description carries most of the behavioral burden and does it well: it discloses pricing (up to $0.01, one request per month), that months saved within 30 days are read free, that the service keeps 12 months, and that a call is charged what it bought after holding estimate plus margin. It also describes the refusal path when the maximum exceeds the workspace spend limit and the exact remedy (ask the user, retry with approvedMaxCostUsd). It stops short of stating whether the spend hold is released immediately on failure or how long a refused call takes to resolve, but the money-affecting behavior is unusually well covered.

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?

It is front-loaded correctly: what you get, then why you'd want it, then retention, then cost, then the spend-limit refusal protocol. The spend-limit sentences are long and repeat the estimate/maximum distinction twice, which is the main source of bloat, but every section is load-bearing.

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?

With an output schema present, return shape needn't be restated, and the definition still covers retention, cost, free-read window and the error/approval path, which is what an agent needs before spending money. The only gap is routing guidance against sibling SERP and rank-history tools, which a tool in this crowded family would benefit from.

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?

Schema description coverage is 100%, so the baseline is 3, and the description earns above that by explaining what 'month' means operationally (one request returns that month's snapshots; the service keeps only the last 12) and by spelling out the approvedMaxCostUsd retry flow in prose. It adds little for keyword, projectId, languageCode or locationCode beyond what the schema already documents.

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 states a specific verb and resource: it returns Google's saved results for a keyword for one past month, including snapshot date, SERP features and top 20 organic results with position, domain, URL and title. The phrase 'Shows who ranked where before, to see whether rankings moved' distinguishes it conceptually from a live-SERP sibling, but no sibling is actually named, so the differentiation is implicit rather than explicit.

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 rather than stated: the tool is for looking at historical rankings over the last 12 months and comparing movement. There is no explicit 'use get_serp_results for current results' or any exclusion/alternative, and no guidance on when a month's snapshot is preferable to a rank-history tool.

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