SEO GSC Wizard MCP

Get ranking changes between two periods

get_ranking_changes

Read-only

Use this when the user asks which queries or pages moved up or down between two periods: each is filed as new, lost, improved or declined (improved = better, lower average position). Not for pages losing clicks over time: use find_decaying_content. limit (1-10000, default 50) applies PER BUCKET; counts gives the full size of each bucket before that cut. Buckets run largest first: improved and declined by the size of positionDelta (prevPosition minus position; a new or lost key's missing side reads 0), new by clicks, lost by prevClicks. ctr is a 0-100 percentage. Each period reads its top scanLimit keys by clicks (warehouse: max(limit*10, 1000), capped at 50000; live API: 25000), and counts are measured within them. The warehouse reads every key in either period's top scanLimit in both periods, so new and lost are real; on the live API the reads are independent, so a key just below one cut can show as new or lost. Query movers are only the queries Google lists: on most properties a large share of clicks has no query row (analyze_sampling_impact measures it). Served from the GSC Wizard 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).

Input Schema

Name	Required	Description	Default
`limit`	No
`endDate`	No	Optional. 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".
`siteUrl`	Yes
`dimension`	No		query
`startDate`	No	Optional. 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".
`searchType`	No	Search type: web (default), image, video, news (the News tab), discover, googleNews (news.google.com), or all (web + image + video + news + discover combined, position impression-weighted, like the app's "All" filter). Discover and googleNews carry no query dimension, so query-level results for them are empty, and no position: it reads null, not 0.	web
`comparisonEndDate`	No	Optional. End of the baseline / comparison period as YYYY-MM-DD. Omit both comparison dates to use the same-length period immediately before the current window; give only this one to end a baseline of the same length here.
`comparisonStartDate`	No	Optional. Start of the baseline / comparison period as YYYY-MM-DD. Omit both comparison dates to use the same-length period immediately before the current window; give only this one to start a baseline of the same length here.

Output Schema

Name	Required	Description
`hint`	No
`kind`	No	Widget variant: "kpis", "table", or "sections".
`kpis`	No	KPI cards (kind="kpis").
`note`	No	Caveat about the result, when the tool returned one.
`rows`	No	Data rows (kind="table").
`notes`	No	Caveats about the result, when the tool returned several.
`scope`	No	The brand, content group or topic cluster filter these numbers are narrowed to; absent when the call was unscoped and the numbers cover the whole property.
`title`	No
`blocks`	No	Stacked sub-blocks (kind="sections").
`reason`	No
`source`	No
`thenBy`	No	Secondary sort field, when the tool states one.
`account`	No
`columns`	No	Column defs (kind="table").
`warning`	No	A caveat that changes how the numbers read.
`coverage`	No	How much of the property total the returned rows cover, with the property totals inline. Quote totals from here; do not sum the rows.
`nextStep`	No
`ordering`	No	Sort order per list, when the result holds several lists.
`sortedBy`	No	Row field the rows are sorted by.
`timeZone`	No	GA4 property's IANA reporting time zone.
`emptyText`	No
`siteScope`	No	Set when GA4 numbers were narrowed to this site's hostnames because the property is shared with other sites.
`sortOrder`	No	"asc" or "desc".
`thenOrder`	No	The tie-break's direction, present only when it differs from sortOrder.
`partialDays`	No	Requested days after settledThrough; their numbers are still incomplete.
`dataMaturity`	No
`emptyBecause`	No
`methodLimits`	No
`notConfigured`	No
`reauthRequired`	No
`settledThrough`	No	Last day the data is complete through.
`comparisonHasData`	No	false when the comparison period has no data at all, so there is no comparison.
`coverageUnavailable`	No	Why coverage is null, when it is.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

changedInput schema / properties / searchType / description

Previous value: -"Search type: web (default), image, video, news (the News tab), discover, googleNews (news.google.com), or all (web + image + video + news + discover combined, position impression-weighted, like the app's \"All\" filter). Discover and googleNews carry no query dimension, so query-level results for them are empty."New value: +"Search type: web (default), image, video, news (the News tab), discover, googleNews (news.google.com), or all (web + image + video + news + discover combined, position impression-weighted, like the app's \"All\" filter). Discover and googleNews carry no query dimension, so query-level results for them are empty, and no position: it reads null, not 0."

Changed2 schema fields changedOct 25, 2026

addedInput schema / properties / searchType / description

Added value: +"Search type: web (default), image, video, news (the News tab), discover, googleNews (news.google.com), or all (web + image + video + news + discover combined, position impression-weighted, like the app's \"All\" filter). Discover and googleNews carry no query dimension, so query-level results for them are empty."

changedInput schema / properties / searchType / enum

Previous value: -[
-  "web",
-  "image",
-  "video",
-  "news"
-]New value: +[
+  "web",
+  "image",
+  "video",
+  "news",
+  "discover",
+  "googleNews",
+  "all"
+]

Changed21 schema fields changedOct 18, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / account

Added value: +{
+  "$ref": "#/properties/title"
+}

addedOutput schema / properties / coverage

Added value: +{
+  "description": "How much of the property total the returned rows cover, with the property totals inline. Quote totals from here; do not sum the rows."
+}

addedOutput schema / properties / coverageUnavailable

Added value: +{
+  "$ref": "#/properties/kind",
+  "description": "Why coverage is null, when it is."
+}

changedOutput schema / properties / dataMaturity / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "dateBasis": {
-        "$ref": "#/properties/title"
-      },
-      "firstIncompleteDate": {
-        "$ref": "#/properties/title"
-      },
-      "note": {
-        "$ref": "#/properties/title"
-      },
-      "probe": {
-        "anyOf": [
-          {
-            "additionalProperties": false,
-            "properties": {
-              "dataState": {
-                "$ref": "#/properties/title"
-              },
-              "endDate": {
-                "$ref": "#/properties/title"
-              },
-              "searchType": {
-                "$ref": "#/properties/title"
-              },
-              "startDate": {
-                "$ref": "#/properties/title"
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "settledThrough": {
-        "$ref": "#/properties/title"
-      },
-      "source": {
-        "$ref": "#/properties/title"
-      },
-      "warehouseCutoff": {
-        "$ref": "#/properties/title"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "dateBasis": {
+        "$ref": "#/properties/title"
+      },
+      "firstIncompleteDate": {
+        "$ref": "#/properties/title"
+      },
+      "note": {
+        "$ref": "#/properties/title"
+      },
+      "probe": {
+        "anyOf": [
+          {
+            "additionalProperties": true,
+            "properties": {
+              "dataState": {
+                "$ref": "#/properties/title"
+              },
+              "endDate": {
+                "$ref": "#/properties/title"
+              },
+              "searchType": {
+                "$ref": "#/properties/title"
+              },
+              "startDate": {
+                "$ref": "#/properties/title"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "settledThrough": {
+        "$ref": "#/properties/title"
+      },
+      "source": {
+        "$ref": "#/properties/title"
+      },
+      "warehouseCutoff": {
+        "$ref": "#/properties/title"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / emptyBecause

Added value: +{
+  "$ref": "#/properties/title"
+}

addedOutput schema / properties / hint

Added value: +{
+  "$ref": "#/properties/title"
+}

addedOutput schema / properties / methodLimits

Added value: +{
+  "$ref": "#/properties/title"
+}

addedOutput schema / properties / nextStep

Added value: +{
+  "$ref": "#/properties/title"
+}

addedOutput schema / properties / notConfigured

Added value: +{
+  "$ref": "#/properties/comparisonHasData"
+}

addedOutput schema / properties / ordering

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "additionalProperties": true,
+        "properties": {
+          "sortOrder": {
+            "$ref": "#/properties/title"
+          },
+          "sortedBy": {
+            "$ref": "#/properties/title"
+          },
+          "thenBy": {
+            "$ref": "#/properties/title"
+          },
+          "thenOrder": {
+            "$ref": "#/properties/title"
+          }
+        },
+        "type": "object"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Sort order per list, when the result holds several lists."
+}

addedOutput schema / properties / partialDays

Added value: +{
+  "$ref": "#/properties/siteScope/anyOf/0/properties/hostnames",
+  "description": "Requested days after settledThrough; their numbers are still incomplete."
+}

addedOutput schema / properties / reason

Added value: +{
+  "$ref": "#/properties/title"
+}

addedOutput schema / properties / reauthRequired

Added value: +{
+  "$ref": "#/properties/notConfigured"
+}

addedOutput schema / properties / scope

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {
+        "brand": {
+          "$ref": "#/properties/kind",
+          "description": "\"branded\" or \"non_branded\"."
+        },
+        "brandKeywordsSkipped": {
+          "$ref": "#/properties/siteScope/anyOf/0/properties/hostnames",
+          "description": "Branded keywords that could not be compiled and were left out of the filter."
+        },
+        "contentGroup": {
+          "anyOf": [
+            {
+              "additionalProperties": true,
+              "properties": {
+                "id": {
+                  "$ref": "#/properties/title"
+                },
+                "name": {
+                  "$ref": "#/properties/title"
+                }
+              },
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "topicCluster": {
+          "anyOf": [
+            {
+              "additionalProperties": true,
+              "properties": {
+                "id": {
+                  "$ref": "#/properties/title"
+                },
+                "name": {
+                  "$ref": "#/properties/title"
+                }
+              },
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The brand, content group or topic cluster filter these numbers are narrowed to; absent when the call was unscoped and the numbers cover the whole property."
+}

changedOutput schema / properties / siteScope / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "hostnames": {
-        "anyOf": [
-          {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "includesSubdomainsOf": {
-        "$ref": "#/properties/title"
-      },
-      "note": {
-        "$ref": "#/properties/title"
-      },
-      "sharedWithSites": {
-        "$ref": "#/properties/siteScope/anyOf/0/properties/hostnames"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "hostnames": {
+        "anyOf": [
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "includesSubdomainsOf": {
+        "$ref": "#/properties/title"
+      },
+      "note": {
+        "$ref": "#/properties/title"
+      },
+      "sharedWithSites": {
+        "$ref": "#/properties/siteScope/anyOf/0/properties/hostnames"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / sortOrder

Added value: +{
+  "$ref": "#/properties/kind",
+  "description": "\"asc\" or \"desc\"."
+}

addedOutput schema / properties / sortedBy

Added value: +{
+  "$ref": "#/properties/kind",
+  "description": "Row field the rows are sorted by."
+}

addedOutput schema / properties / thenBy

Added value: +{
+  "$ref": "#/properties/kind",
+  "description": "Secondary sort field, when the tool states one."
+}

addedOutput schema / properties / thenOrder

Added value: +{
+  "$ref": "#/properties/kind",
+  "description": "The tie-break's direction, present only when it differs from sortOrder."
+}

addedOutput schema / properties / warning

Added value: +{
+  "$ref": "#/properties/kind",
+  "description": "A caveat that changes how the numbers read."
+}

Changed2 schema fields changedOct 10, 2026

changedInput schema / properties / comparisonEndDate / description

Previous value: -"Optional. End of the baseline / comparison period as YYYY-MM-DD. Omit both comparison dates to use the same-length period immediately before the current window."New value: +"Optional. End of the baseline / comparison period as YYYY-MM-DD. Omit both comparison dates to use the same-length period immediately before the current window; give only this one to end a baseline of the same length here."

changedInput schema / properties / comparisonStartDate / description

Previous value: -"Optional. Start of the baseline / comparison period as YYYY-MM-DD. Omit both comparison dates to use the same-length period immediately before the current window."New value: +"Optional. Start of the baseline / comparison period as YYYY-MM-DD. Omit both comparison dates to use the same-length period immediately before the current window; give only this one to start a baseline of the same length here."

Changed4 schema fields changedOct 7, 2026

addedOutput schema / properties / comparisonHasData

Added value: +{
+  "description": "false when the comparison period has no data at all, so there is no comparison.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / note

Added value: +{
+  "$ref": "#/properties/kind",
+  "description": "Caveat about the result, when the tool returned one."
+}

addedOutput schema / properties / notes

Added value: +{
+  "$ref": "#/properties/siteScope/anyOf/0/properties/hostnames",
+  "description": "Caveats about the result, when the tool returned several."
+}

addedOutput schema / properties / siteScope

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "hostnames": {
+          "anyOf": [
+            {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "includesSubdomainsOf": {
+          "$ref": "#/properties/title"
+        },
+        "note": {
+          "$ref": "#/properties/title"
+        },
+        "sharedWithSites": {
+          "$ref": "#/properties/siteScope/anyOf/0/properties/hostnames"
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Set when GA4 numbers were narrowed to this site's hostnames because the property is shared with other sites."
+}

First observedOct 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare readOnly/openWorld/non-destructive, but the description adds substantial non-obvious behavior: per-bucket bucketing semantics, sort order within buckets, warehouse-vs-live-API differences in how new/lost are computed, scanLimit expansion, sampling gaps on query rows, and a 2-3 day data lag. This is context no annotation could 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 use-when case, and nearly every sentence carries genuinely useful caveats. It is dense and runs as one block rather than being segmented by concern, so an agent has to parse carefully, but there is little filler to cut.

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 complex cross-period comparison tool with an output schema present, the description covers sourcing, bucketing rules, fallback behavior, sampling caveats, and defaults. Nothing needed to invoke it correctly appears 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 63%, and the description fills the gap with critical meaning: `limit` applies per bucket (not globally), `counts` reports full bucket sizes before that cut, `ctr` is 0-100, `scanLimit` derivation per source, and the omit-dates default of the last 28 settled days. These are interpretations the schema does not provide.

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 — queries or pages that moved up or down between two periods — and instantly names the sibling it is not for (find_decaying_content). An agent can distinguish this from find_decaying_content and detect_change_points without opening the 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?

Explicit routing: 'Use this when the user asks which queries or pages moved up or down between two periods' plus an explicit exclusion ('Not for pages losing clicks over time: use find_decaying_content'). The alternative and the condition selecting it are both stated, plus the default-with-no-dates case is covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SEO GSC Wizard MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?