SEO GSC Wizard MCP

Topic cluster performance

get_topic_cluster_performance

Read-only

Use this when the user asks how a property's topic clusters perform: clicks, impressions, CTR (0-100), impression-weighted average position, matched query count and share of clicks (clickShare, 0-100) per cluster, plus an "unclustered" bucket for queries no cluster claims. Not for the cluster definitions: use list_topic_clusters (create_topic_cluster adds one). Pass clusterId to drill into one cluster's top queries (each row lists which of the cluster's keywords matched). A cluster keyword is a case-insensitive substring unless wrapped in slashes (/seo ?tools/), which makes it a regex. IMPORTANT: clusters may OVERLAP (a query matching two clusters counts fully in both), so cluster totals do not sum to the property total; overlappingQueries reports how many queries are double-counted. Shares are of visible queries only: coverage.hiddenClicksShare (0-1) is the share of the property's clicks with no query row. Clusters are listed by name; drill-down queries by clicks, highest first. Matching runs over the top scanLimit queries by clicks (default 50,000), read from the GSC Wizard ClickHouse warehouse when available (which scans at most 50,000 queries; scanLimit in the response is the limit actually applied), 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	Row cap for the clusterId query drill-down.
`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
`clusterId`	No	Drill into one cluster: returns its top matched queries instead of the per-cluster aggregates. Accepts a topic cluster id or the literal "unclustered".
`scanLimit`	No	How many top queries by clicks to match against the clusters. Raise it when a long-tail property reports `truncated: true`. Clamped at 50,000 on the ClickHouse path.
`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 comparison period as YYYY-MM-DD. Provide BOTH comparison dates to compare two periods; omit both for no comparison (prev* fields are then 0 and hasComparison false).
`comparisonStartDate`	No	Optional. Start of the comparison period as YYYY-MM-DD. Provide BOTH comparison dates to compare two periods; omit both for no comparison (prev* fields are then 0 and hasComparison false).

Output Schema

Name	Required	Description
`note`	No
`range`	No
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`queries`	No
`siteUrl`	No
`warning`	No
`clusters`	No
`coverage`	No	How much of the property total the rows cover, totals inline. Quote totals from here; do not sum rows.
`nextStep`	No
`ordering`	No
`sortedBy`	No
`clusterId`	No
`scanLimit`	No
`sortOrder`	No
`thenOrder`	No
`truncated`	No
`dataSource`	No
`searchType`	No
`clusterName`	No
`overlapNote`	No
`partialDays`	No
`unclustered`	No
`clusterCount`	No
`dataMaturity`	No
`emptyBecause`	No
`methodLimits`	No
`hasComparison`	No
`scannedClicks`	No
`scannedQueries`	No
`settledThrough`	No
`comparisonRange`	No
`matchedQueryCount`	No
`overlappingQueries`	No
`coverageUnavailable`	No	Why coverage is null, when it is.
`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 / clusters / items / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / coverage

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {
+        "clicksCovered": {
+          "$ref": "#/properties/range/anyOf/0/properties/days",
+          "description": "0-1 share of the totals named by sharesOf that this page's rows carry."
+        },
+        "filteredTotals": {
+          "$ref": "#/properties/coverage/anyOf/0/properties/siteTotals",
+          "description": "The same totals with the filters applied (scope \"filtered\")."
+        },
+        "hiddenClicksShare": {
+          "$ref": "#/properties/range/anyOf/0/properties/days",
+          "description": "0-1 share of those totals that no row of this dimension carries (anonymised queries on query rows, near zero on page, country and device rows); null when unknown."
+        },
+        "hiddenImpressionsShare": {
+          "$ref": "#/properties/range/anyOf/0/properties/days"
+        },
+        "impressionsCovered": {
+          "$ref": "#/properties/range/anyOf/0/properties/days"
+        },
+        "note": {
+          "$ref": "#/properties/siteUrl",
+          "description": "Why some fields are null, when they are."
+        },
+        "rowsReturned": {
+          "$ref": "#/properties/range/anyOf/0/properties/days",
+          "description": "Rows on this page."
+        },
+        "rowsTotal": {
+          "$ref": "#/properties/range/anyOf/0/properties/days",
+          "description": "Rows across every page; null when unknown."
+        },
+        "scope": {
+          "$ref": "#/properties/siteUrl",
+          "description": "\"property\", or \"filtered\" when the rows were read with filters."
+        },
+        "sharesOf": {
+          "$ref": "#/properties/siteUrl",
+          "description": "\"siteTotals\", or \"filteredTotals\" when scope is \"filtered\"."
+        },
+        "siteTotals": {
+          "anyOf": [
+            {
+              "additionalProperties": true,
+              "properties": {
+                "avgPositionWeighted": {
+                  "$ref": "#/properties/range/anyOf/0/properties/days",
+                  "description": "Impression-weighted average position."
+                },
+                "clicks": {
+                  "$ref": "#/properties/range/anyOf/0/properties/days"
+                },
+                "ctrPercent": {
+                  "$ref": "#/properties/range/anyOf/0/properties/days",
+                  "description": "A 0-100 percentage."
+                },
+                "impressions": {
+                  "$ref": "#/properties/range/anyOf/0/properties/days"
+                }
+              },
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The property's totals for this window and search type, with no dimension and no filter."
+        },
+        "totalsFrom": {
+          "$ref": "#/properties/siteUrl",
+          "description": "\"get_site_summary\" (the read and arithmetic that tool uses) or \"property_totals\" (the same, for a search type other than web)."
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "How much of the property total the rows cover, totals inline. Quote totals from here; do not sum rows."
+}

addedOutput schema / properties / coverageUnavailable

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

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

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: +{
+  "$ref": "#/properties/queries/items/properties/matchedKeywords"
+}

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

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 / unclustered / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "clickShare": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "clicks": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "clusterId": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "ctr": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "impressions": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "keywordCount": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "name": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "position": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "prevClicks": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "prevCtr": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "prevImpressions": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "prevPosition": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "queries": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "clickShare": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "clicks": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "clusterId": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "ctr": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "impressions": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "keywordCount": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "name": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "position": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "prevClicks": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "prevCtr": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "prevImpressions": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "prevPosition": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "queries": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / warning

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

Changed1 schema field changedOct 10, 2026
- 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 readOnly/openWorld annotations: discloses that clusters may OVERLAP so totals do not sum to the property total, that overlappingQueries reports double-counting, that shares are of visible queries only with a hiddenClicksShare escape hatch, the sort orders for clusters vs drill-down, the ClickHouse-vs-live-API data source selection and 50,000 clamp, and the ~2-3 day data lag. These are decision-affecting traits an agent cannot infer from annotations or schema.

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 trigger condition and metric list, then progressively deeper caveats. Every sentence carries non-obvious information (overlap semantics, matching rules, data source), though the single dense paragraph would be easier to scan if the caveats were broken into shorter sentences.

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 9-parameter analytical tool with an output schema, the description covers what the agent needs: semantics of overlap, the unclustered bucket, hidden-query coverage, sorting, data-source fallback, and default date window. It even explains the meaning of response fields (overlappingQueries, coverage.hiddenClicksShare, dataSource, truncated) rather than relying solely on the output schema.

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 already 89%, so the schema carries most parameter documentation (startDate/endDate defaults, searchType enum, scanLimit clamp). The description still adds interpretive meaning: clusterId switches the response shape entirely, date omission defaults to 28 settled days, and scanLimit governs which queries are matched. Only mildly redundant with the schema text.

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 (topic cluster performance for a property) and immediately enumerates the metrics returned (clicks, impressions, CTR, position, matched query count, clickShare). It explicitly contrasts itself with list_topic_clusters and create_topic_cluster, so an agent can distinguish it from siblings 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?

"Use this when the user asks how a property's topic clusters perform" gives a clear triggering condition, and "Not for the cluster definitions: use list_topic_clusters (create_topic_cluster adds one)" names the exact alternatives and what they do instead. It also states when to pass clusterId (drill into one cluster's top queries).

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?