SEO GSC Wizard MCP

Ranking position distribution

get_position_distribution

Read-only

Use this when the user asks how much visibility sits in the top 3, on page one or deeper: slices a property by where it ranks, using the same 1-3 / 4-10 / 11-20 / 21+ bands as the GSC Wizard dashboard. Not for CTR by position: use analyze_ctr_curve. granularity "period" (default) returns impressions, clicks and the number of queries (or pages) in each band over the whole range. granularity "daily" returns one row per day with the count of DISTINCT queries ranking in each band, to see a ranking shift build up or a drop land on a date. Bands run best first (1-3 to 21+) and days oldest first; ctr and the shares are 0-100 percentages. By query, counts and shares cover only the queries Google lists: on most properties a large share of clicks has no query row (analyze_sampling_impact measures it). 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 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

Name	Required	Description	Default
`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	What a "row" is on the period path: a search query or a page.	query
`scanLimit`	No	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.
`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
`granularity`	No	"period" = one bucket summary over the range; "daily" = distinct query counts per band per day (always keyed on query, ignores `dimension`).	period

Output Schema

Name	Required	Description
`days`	No
`note`	No
`range`	No
`thenBy`	No
`totals`	No
`buckets`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`siteUrl`	No
`warning`	No
`nextStep`	No
`ordering`	No
`sortedBy`	No
`dayTotals`	No
`dimension`	No
`scanLimit`	No
`sortOrder`	No
`thenOrder`	No
`truncated`	No
`dataSource`	No
`searchType`	No
`granularity`	No
`partialDays`	No
`dataMaturity`	No
`emptyBecause`	No
`methodLimits`	No
`settledThrough`	No
`warehouseLatestDate`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / listKey

Added value: +{
+  "$ref": "#/properties/siteUrl",
+  "description": "Name of the top-level field that holds the rows sortedBy describes."
+}

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"
+]

Changed18 schema fields changedOct 18, 2026

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

addedOutput schema / properties / buckets / items / properties / bandOrder

Added value: +{
+  "$ref": "#/properties/range/anyOf/0/properties/days",
+  "description": "1-based place of the band, best first: 1 is 1-3, 4 is 21+."
+}

changedOutput schema / properties / dataMaturity / anyOf

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

changedOutput schema / properties / dayTotals / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "clicks": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "date": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "deep": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "first": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "impressions": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "second": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "top3": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "total": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "clicks": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "date": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "deep": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "first": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "impressions": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "second": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "top3": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "total": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

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

addedOutput schema / properties / emptyBecause

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

addedOutput schema / properties / methodLimits

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

addedOutput schema / properties / nextStep

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

addedOutput schema / properties / ordering

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "additionalProperties": true,
+        "properties": {
+          "sortOrder": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "sortedBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenOrder": {
+            "$ref": "#/properties/siteUrl"
+          }
+        },
+        "type": "object"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / partialDays

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / range / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "days": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "endDate": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "startDate": {
-        "$ref": "#/properties/siteUrl"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "days": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "endDate": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "startDate": {
+        "$ref": "#/properties/siteUrl"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / sortOrder

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

addedOutput schema / properties / sortedBy

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

addedOutput schema / properties / thenBy

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

addedOutput schema / properties / thenOrder

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

changedOutput schema / properties / totals / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "clicks": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "impressions": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "rows": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "clicks": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "impressions": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "rows": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / warning

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

Changed2 schema fields changedOct 10, 2026

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"
+}

First observedOct 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: it discloses the dual data source (ClickHouse warehouse vs. live GSC API), that scanLimit is null on the warehouse, that truncation drops zero-click rows and understates deep bands, and the ~2-3 day data lag. These are non-obvious failure modes the agent needs before interpreting results.

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?

Long but front-loaded: the trigger and the sibling exclusion come first, then output ordering, then data-source caveats. Nearly every sentence carries information, though the warehouse/truncation passage is dense and could be tightened.

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 read-only analytics tool with an output schema and annotations, this covers all the remaining gaps an agent needs: band definitions, ordering, percentage scale, data-source caveats, truncation effects, and date-range defaults with lag.

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 86%, so the schema already documents most params; the description still adds value by explaining what granularity 'daily' returns (distinct query counts per band per day, ignoring dimension), band/day ordering, and that ctr and shares are 0-100 percentages. That is meaningful semantics beyond the schema, though siteUrl and date params are left to the schema.

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: slices a property by ranking position into the 1-3 / 4-10 / 11-20 / 21+ bands. It immediately names the sibling it is not (analyze_ctr_curve for CTR by position), so the agent can distinguish it 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?

Opens with an explicit trigger ('Use this when the user asks how much visibility sits in the top 3, on page one or deeper') and names an exclusion with the alternative tool. The period-vs-daily guidance also tells the agent which mode fits which intent (ranking shift build-up vs. drop on a date).

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?