Skip to main content
Glama

SEO GSC Wizard MCP

Ranking position distribution

get_position_distribution
Read-only

Slices a property by where it ranks, using the same 1-3 / 4-10 / 11-20 / 21+ bands as the GSC Wizard dashboard. granularity "period" (default) returns impressions, clicks and the number of queries (or pages) in each band over the whole range, showing how top-heavy the property's visibility is. granularity "daily" returns one row per day with the count of DISTINCT queries ranking in each band, which is how you see a ranking shift build up or a drop land on a specific date. Positions are impression-weighted averages, so a row sits in one band only. Served from the GSC Wizard ClickHouse warehouse when available (both views are computed in the warehouse over every query or page, never truncated; scanLimit is null there), otherwise from the live Search Console API over the top scanLimit rows by clicks, which drops zero-click rows first and so understates the deep bands when truncated is true (see dataSource). Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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".
siteUrlYes
dimensionNoWhat a "row" is on the period path: a search query or a page.query
scanLimitNoHow many top rows by clicks to bucket on the live Search Console API. Raise it when a long-tail property reports `truncated: true`. Ignored on the ClickHouse warehouse, which buckets every row in SQL.
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".
searchTypeNoweb
granularityNo"period" = one bucket summary over the range; "daily" = distinct query counts per band per day (always keyed on query, ignores `dimension`).period

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo
noteNo
rangeNo
totalsNo
bucketsNo
siteUrlNo
dayTotalsNo
dimensionNo
scanLimitNo
truncatedNo
dataSourceNo
searchTypeNo
granularityNo
dataMaturityNo
settledThroughNo
warehouseLatestDateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / scanLimit / description
      Previous value: -"How many top rows by clicks to bucket. Raise it when a long-tail property reports `truncated: true`. The ClickHouse period path clamps it at 50,000; ignored by the ClickHouse daily path, which aggregates in SQL."New value: +"How many top rows by clicks to bucket on the live Search Console API. Raise it when a long-tail property reports `truncated: true`. Ignored on the ClickHouse warehouse, which buckets every row in SQL."
    • addedOutput schema / properties / warehouseLatestDate
      Added value: +{
      +  "$ref": "#/properties/siteUrl"
      +}
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources