SEO GSC Wizard MCP

GA4 breakdown report

query_ga4_report

Read-only

Use this when the user asks how a site's GA4 traffic splits by one dimension. Runs ONE GA4 dimension breakdown for the property linked to a GSC Wizard site: channel, sourceMedium, page, landingPage, country, device, event, date (daily trend), hostName, firstUserChannel or firstUserSourceMedium. channel and sourceMedium attribute each session to its own source; firstUserChannel and firstUserSourceMedium attribute users to the source that first acquired them, as GA4's User acquisition report does (use those when the user asks about new users or first-user attribution). Each dimension carries its own metric set (returned in metrics); rows are sorted by the first metric, highest first (date breakdowns by date, oldest first). Not for site totals: use get_ga4_overview (rows stop at limit; do not sum them). Set secondaryDimension to "date" or "hostName" to split every row further, e.g. dimension "event" + secondaryDimension "date" shows on which days an event fired; each row then carries that field (dates as YYYY-MM-DD). Rows include prev* fields that are only meaningful when a comparison range is given (hasComparison); date breakdowns take no comparison range. Only the first limit rows are returned (truncated and note say when more exist); to follow one event, pass filters: { event: [""] }. When the GA4 property is shared with other sites, results are limited to this site's hostnames and siteScope says so (on a shared property a hostName filter narrows within that scope; only the owner can replace it). Rates (engagementRate, bounceRate) are fractions 0-1, not percentages. Returns notConfigured (not an error) when Google Analytics is not connected or no GA4 property is linked to the site in GSC Wizard. Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).

Input Schema

Name	Required	Description
`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".
`filters`	No	Optional GA4 dimension filters applied to every report in the call. Within a list field the values OR together; different fields AND together. Omit entirely for unfiltered data.
`siteUrl`	Yes
`dimension`	Yes
`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".
`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).
`secondaryDimension`	No	Optional second dimension that splits every row: "date" (per day) or "hostName" (per site/stream host). Must differ from `dimension`.
`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
`hint`	No
`note`	No
`rows`	No
`range`	No
`reason`	No
`thenBy`	No
`account`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`metrics`	No
`siteUrl`	No
`nextStep`	No
`ordering`	No
`rowCount`	No
`sortedBy`	No
`timeZone`	No
`dimension`	No
`siteScope`	No
`sortOrder`	No
`thenOrder`	No
`totalRows`	No
`truncated`	No
`dataSource`	No
`propertyId`	No
`emptyBecause`	No
`methodLimits`	No
`hasComparison`	No
`notConfigured`	No
`reauthRequired`	No
`comparisonRange`	No
`secondaryDimension`	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."
+}

Changed3 schema fields changedOct 27, 2026

changedInput schema / properties / dimension / enum

Previous value: -[
-  "channel",
-  "sourceMedium",
-  "page",
-  "landingPage",
-  "country",
-  "device",
-  "event",
-  "date",
-  "hostName"
-]New value: +[
+  "channel",
+  "sourceMedium",
+  "page",
+  "landingPage",
+  "country",
+  "device",
+  "event",
+  "date",
+  "hostName",
+  "firstUserChannel",
+  "firstUserSourceMedium"
+]

addedInput schema / properties / filters / properties / firstUserChannel

Added value: +{
+  "description": "GA4 firstUserDefaultChannelGroup names, matched exactly (any of): the channel that first acquired the user, as in GA4's User acquisition report, rather than the session's own channel. E.g. [\"Organic Search\"].",
+  "items": {
+    "maxLength": 256,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 300,
+  "type": "array"
+}

addedInput schema / properties / filters / properties / firstUserSourceMedium

Added value: +{
+  "description": "GA4 firstUserSourceMedium values, matched exactly (any of): the source / medium that first acquired the user (User acquisition report), e.g. [\"google / organic\"].",
+  "items": {
+    "maxLength": 256,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 300,
+  "type": "array"
+}

Changed11 schema fields changedOct 18, 2026

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

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

changedOutput schema / properties / siteScope / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "hostnames": {
-        "anyOf": [
-          {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "includesSubdomainsOf": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "note": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "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/siteUrl"
+      },
+      "note": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "sharedWithSites": {
+        "$ref": "#/properties/siteScope/anyOf/0/properties/hostnames"
+      }
+    },
+    "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"
+}

Changed2 schema fields changedOct 10, 2026

changedInput schema / properties / filters / properties / hostName / description

Previous value: -"GA4 hostName values, matched exactly (any of), e.g. [\"www.example.com\"]. When the linked GA4 property is shared with other sites, results are already limited to this site's hostnames (see `siteScope` in the response); setting hostName replaces that automatic scope, e.g. to read another stream or several hosts at once."New value: +"GA4 hostName values, matched exactly (any of), e.g. [\"www.example.com\"]. When the linked GA4 property is shared with other sites, results are already limited to this site's hostnames (see `siteScope` in the response). For the property owner, setting hostName replaces that automatic scope, e.g. to read another stream or several hosts at once; on a property shared with you it only narrows within the scope."

addedOutput schema / properties / reauthRequired

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

Changed2 schema fields changedOct 8, 2026
- addedOutput schema / properties / note
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```
- addedOutput schema / properties / truncated
```
Added value: +{
+  "$ref": "#/properties/hasComparison"
+}
```

Changed7 schema fields changedOct 7, 2026

changedInput schema / properties / dimension / enum

Previous value: -[
-  "channel",
-  "sourceMedium",
-  "page",
-  "landingPage",
-  "country",
-  "device",
-  "event"
-]New value: +[
+  "channel",
+  "sourceMedium",
+  "page",
+  "landingPage",
+  "country",
+  "device",
+  "event",
+  "date",
+  "hostName"
+]

addedInput schema / properties / filters / properties / hostName

Added value: +{
+  "description": "GA4 hostName values, matched exactly (any of), e.g. [\"www.example.com\"]. When the linked GA4 property is shared with other sites, results are already limited to this site's hostnames (see `siteScope` in the response); setting hostName replaces that automatic scope, e.g. to read another stream or several hosts at once.",
+  "items": {
+    "maxLength": 256,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 300,
+  "type": "array"
+}

addedInput schema / properties / secondaryDimension

Added value: +{
+  "description": "Optional second dimension that splits every row: \"date\" (per day) or \"hostName\" (per site/stream host). Must differ from `dimension`.",
+  "enum": [
+    "date",
+    "hostName"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / metrics / $ref

Added value: +"#/properties/siteScope/anyOf/0/properties/hostnames"

removedOutput schema / properties / metrics / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / secondaryDimension

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

addedOutput schema / properties / siteScope

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

First observedOct 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnly/openWorld/non-destructive; the description adds substantial behavioral context beyond that: rows sorted by first metric (date breakdowns oldest first), hard row cap at `limit` with `truncated`/`note` signals, prev* fields inert without a comparison range, date breakdowns rejecting comparisons, shared-property `siteScope` narrowing and owner-only override, rates as 0-1 fractions, ~2-3 day data lag, and `notConfigured` returned as a non-error.

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 case and the sibling exclusion, and almost every sentence carries non-obvious information (truncation, siteScope, rate units, notConfigured). However, it is a single dense paragraph of ~300 words with some repetition of the limit/truncation and date-range points, which makes it harder to scan than it needs to be.

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 tool with nested filters, enums, and an output schema, the description covers the decision points an agent needs: which dimension to pick, how to drill down, how dates default, what limits results, and what non-error states look like. Nothing required to call it correctly is missing, and return-shape detail is rightly left to 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?

With 67% schema coverage the schema already documents dates, comparisons, secondaryDimension and the filter operators, so credit goes to what the description adds: the semantic difference between channel/sourceMedium and firstUserChannel/firstUserSourceMedium, the meaning of the 'date' dimension (daily trend), the default 28 settled days when both dates are omitted, the secondaryDimension split example, and the comparison restriction on date breakdowns. It leaves limit bounds, siteUrl, and the pagePath operator semantics 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 action (run ONE GA4 dimension breakdown for the property linked to a GSC Wizard site) and enumerates the exact supported dimensions. It also explicitly contrasts itself with get_ga4_overview (site totals) and explains the channel vs. firstUserChannel distinction, so an agent can pick it out of a large sibling set without reading 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 a use condition ('when the user asks how a site's GA4 traffic splits by one dimension') and names the correct alternative for the adjacent case ('Not for site totals: use get_ga4_overview'). It further routes intent: use firstUserChannel/firstUserSourceMedium when the user asks about new users or first-user attribution.

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?