Skip to main content
Glama

Rank Checker by GSC Wizard

Get Rank Checker positions

get_rank_keyword_data
Read-only

Use this when the user asks how their tracked keywords rank, which moved, or for the ranking history of a keyword. Reads the data points the GSC Wizard Rank Checker collected for one keyword set (setId from list_rank_keyword_sets): Search Console average positions for the set's country and device, stored once a day. Without keyword: every keyword's impression-weighted position, clicks and impressions over the period (days: 7, 28, 91, 182, 365 or 485; default 7) against the same number of days before, with the change (positive = better) and the ranking URL, plus the daily trend of the set (average position, top 3 / top 10 counts). period.comparable is false when the period before starts earlier than the stored history (period.storedFrom): then there is no previous position, change, new or lost. With keyword: that keyword's daily data points over the period. Lower position is better. Not for keywords outside a set: use get_query_performance.

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>",
      "setId": "<setId>"
    },
    "name": "get_rank_keyword_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoPeriod length: 7 (default), 28, 91, 182, 365 or 485 days.
setIdYes
keywordNoOne keyword of the set: returns its daily data points instead.
siteUrlYes

Output Schema

NameRequiredDescriptionDefault
setIdNo
trendNo
deviceNo
periodNo
countryNo
historyNo
keywordNo
setNameNo
siteUrlNo
keywordsNo
nextStepNo
emptyBecauseNo
methodLimitsNo
lastCheckedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare a safe read, and the description goes well beyond them: data is stored once a day, comparisons run against the same prior period, positive change means improvement while lower position is better, and period.comparable is false when the prior window predates storedFrom (yielding no previous position, change, new or lost). That edge-case behavior is exactly the kind of disclosure annotations cannot carry.

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 usage trigger before mechanics, which is the right order, and nearly every clause carries information. It is, however, a dense multi-clause run-on where the two return-shape branches (with/without keyword) would be clearer as separate sentences or bullets.

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?

Covers the full path an agent needs: trigger, prerequisite lookup, parameter effects on return shape, period semantics, and the comparability edge case, even though an output schema exists. Nothing material about calling it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the description compensates: it gives the default of 7 days for the days enum, explains that passing keyword switches the response to that keyword's daily data points, and identifies setId's source tool. Only siteUrl is left implicit, which is acceptable for a self-evident domain parameter.

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 and resource: reads Rank Checker data points for one keyword set, and names exactly what is returned (impression-weighted positions, clicks, impressions, daily trend). It explicitly separates itself from get_query_performance for keywords outside a set, so an agent can route without opening schemas.

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?

Opens with an explicit trigger ('when the user asks how their tracked keywords rank, which moved, or for the ranking history'), supplies the prerequisite that setId comes from list_rank_keyword_sets, and names the exclusion case plus the alternative tool. When-to-use, prerequisite, and when-not-to-use are all covered.

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.