SEO GSC Wizard MCP

GA4 ecommerce report

get_ga4_ecommerce

Read-only

Use this when the user asks about GA4 revenue, transactions or top-selling products. GA4 ecommerce performance for the property linked to a GSC Wizard site: a revenue / transactions / purchasers summary plus channel, source-medium, page, landing-page, and product (itemName) breakdowns, each sorted by revenue, highest first (totalRevenue; items by itemRevenue). Not for a non-purchase conversion such as a form submit: use get_ga4_key_events. Revenue is in the property currency (currencyCode). hasEcommerce is false when the property shows no ecommerce activity in the period. When active filters are incompatible with the item-scoped Products report, itemsFilterSkipped is true and items is unfiltered while every other table reflects the filters. totalRows gives the full row count of every table before limit. 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
`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).
`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
`items`	No
`pages`	No
`range`	No
`reason`	No
`thenBy`	No
`account`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`siteUrl`	No
`sources`	No
`channels`	No
`nextStep`	No
`ordering`	No
`sortedBy`	No
`timeZone`	No
`siteScope`	No
`sortOrder`	No
`thenOrder`	No
`totalRows`	No
`dataSource`	No
`propertyId`	No
`currencyCode`	No
`emptyBecause`	No
`hasEcommerce`	No
`landingPages`	No
`methodLimits`	No
`hasComparison`	No
`notConfigured`	No
`reauthRequired`	No
`comparisonRange`	No
`ecommerceSummary`	No	Metric totals keyed by GA4 metric name.
`itemsFilterSkipped`	No
`propertyDisplayName`	No
`prevEcommerceSummary`	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."
+}

Changed2 schema fields changedOct 27, 2026

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

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

changedOutput schema / properties / totalRows / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "channels": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "items": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "landingPages": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "pages": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "sources": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "channels": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "items": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "landingPages": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "pages": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "sources": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

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 7, 2026

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

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 say read-only/open-world; the description adds substantive behavior: revenue is in `currencyCode`, `hasEcommerce` false means no activity, `itemsFilterSkipped` explains a partial-filter state, `totalRows` is pre-`limit`, and `notConfigured` is a non-error state for unlinked GA. It also discloses the ~2-3 day data lag, so the agent can reason about why recent dates are missing.

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 and the payload, then the exclusion, then the response-field caveats — a sensible order. It is long, and the closing date-range sentence largely repeats the startDate/endDate schema descriptions, which is the only real redundancy.

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?

Despite an existing output schema, the description intentionally explains the fields that change interpretation (`hasEcommerce`, `itemsFilterSkipped`, `totalRows`, `notConfigured`), plus auth/linkage preconditions and date defaults. For a 7-parameter, nested-filter, multi-table report tool, nothing an agent needs before calling is missing.

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?

At 71% schema coverage the schema does most of the work, but the description still adds meaning: the default window when dates are omitted and the settled-data lag, plus the pre-`limit` semantics of `totalRows` and the conditions under which filters silently do not apply to the item-scoped report. Nested `filters` and `siteUrl` semantics 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?

Names a specific resource and content ('GA4 ecommerce performance ... revenue / transactions / purchasers summary plus channel, source-medium, page, landing-page, and product breakdowns'), so an agent knows exactly what comes back. It also states the trigger ('user asks about GA4 revenue, transactions or top-selling products'), which distinguishes it from get_ga4_overview and get_ga4_key_events without opening a 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 positive trigger plus an explicit exclusion: 'Not for a non-purchase conversion such as a form submit: use get_ga4_key_events.' That is the main routing ambiguity in this family, and it is resolved in-line. The default-date instruction ('omit startDate/endDate to analyze the last 28 settled days') further tells the agent how to call it without extra lookups.

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?