Skip to main content
Glama

Rank Checker by GSC Wizard

Query performance over time

get_query_performance
Read-only

Use this when the user asks how one search query performed day by day. Daily performance for a single search query, optionally restricted to one landing page. Useful for tracking position changes after on-page edits. Not for a ranking of queries: use query_top_queries. query (and pageUrl) must match exactly. Rows run by date, oldest first; days without impressions are absent, not zero. ctr is a 0-100 percentage. Served from the ClickHouse warehouse when available, otherwise the live Search Console API (see dataSource). Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).

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": {
      "siteUrl": "<siteUrl>",
      "query": "<query>"
    },
    "name": "get_query_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
endDateNoOptional. Window end as YYYY-MM-DD (e.g. 2026-05-31). You do NOT need to know today's date or the latest available date: omit this and the server uses the latest settled Search Console date (data lags ~2-3 days behind today). Never pass null or the string "null".
pageUrlNo
siteUrlYes
startDateNoOptional. Window start as YYYY-MM-DD (e.g. 2026-05-03). You do NOT need to know today's date. Omit BOTH startDate and endDate to analyze the last 28 settled days automatically (Search Console data lags ~2-3 days). Never pass null or the string "null".
searchTypeNoSearch type: web (default), image, video, news (the News tab), discover, googleNews (news.google.com), webMultimodal (Google Lens, Circle to Search and image uploads; data from 2026-02-20; not part of all), or all (web + image + video + news + discover combined, position impression-weighted, like the app's "All" filter). Discover, googleNews and webMultimodal carry no query dimension, so query-level results for them are empty; Discover and googleNews also carry no position: it reads null, not 0.web

Output Schema

NameRequiredDescriptionDefault
noteNo
dailyNo
queryNo
rangeNo
thenByNo
listKeyNoName of the top-level field that holds the rows sortedBy describes.
pageUrlNo
siteUrlNo
warningNo
nextStepNo
orderingNo
sortedByNo
sortOrderNo
thenOrderNo
dataSourceNo
partialDaysNo
dataMaturityNo
emptyBecauseNo
methodLimitsNo
settledThroughNo
warehouseLatestDateNo

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 declare read-only/open-world/non-destructive; the description goes well beyond them by disclosing the ClickHouse-vs-live-API data source fallback, the ~2-3 day data lag, the 28-day default window, row ordering, absence of zero-impression days, and the 0-100 ctr scale.

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-loads the when-to-use sentence and packs semantic details into short clauses with no filler. It is dense, but each sentence carries distinct operational information; only minor tightening would improve it.

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 filtered time-series lookup with an output schema, nothing essential is missing: match semantics, defaults, data freshness, ordering, and metric units are all covered. The agent can call it correctly and interpret gaps in the series.

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 coverage is 50%, and the description compensates by stating that query and pageUrl must match exactly and that omitting startDate/endDate yields the last 28 settled days. The searchType enum is already fully documented in the schema, so value-add is solid but not exhaustive for siteUrl.

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?

States a specific verb+resource+scope: daily performance for a single search query, optionally narrowed to a landing page. It explicitly names the sibling it is not (query_top_queries) so the agent can disambiguate without opening either schema.

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?

Gives an explicit trigger ('when the user asks how one search query performed day by day') plus a concrete secondary use case (tracking position changes after on-page edits), and an explicit exclusion routing ranking requests to query_top_queries.

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.