SEO GSC Wizard MCP

GA4 key events (conversions)

get_ga4_key_events

Read-only

Use this when the user asks how many conversions (GA4 key events) a site got and which channels, pages or devices drove them. Segments the GA4 property linked to the site on ONE key event (e.g. form_submit): totals, session/user conversion rates, and per channel, source, landing page, page, country and device breakdowns, each sorted by keyEventCount, highest first (eventCount for a plain event). Not for revenue or products: use get_ga4_ecommerce. Also lists the available key events on the property. When keyEvent is omitted, the most active key event in the period is picked automatically. A keyEvent that is not marked as a key event in GA4 returns plain event counts instead (isKeyEvent: false, with a note). A key event whose name has characters other than letters, digits and _ (e.g. "Sign Up") is reported through an event filter instead, with metricMode "event_filter" and a note on what the numbers mean. rawEventCount is the plain count of the event; when GA4 counted fewer key events than that (marked as a key event after it fired, or counted once per session), a note explains the gap. Rates (sessionKeyEventRate, userKeyEventRate) are fractions 0-1, not percentages. Returns notConfigured when Google Analytics is not connected or no GA4 property is linked. 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	Maximum number of rows per breakdown table.
`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
`keyEvent`	No	GA4 key event name to segment on (e.g. form_submit). Omit to pick the most active key event of the period automatically; the response lists all available names.
`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
`pages`	No
`range`	No
`reason`	No
`thenBy`	No
`account`	No
`devices`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`siteUrl`	No
`sources`	No
`summary`	No	Metric totals keyed by GA4 metric name.
`channels`	No
`keyEvent`	No
`nextStep`	No
`ordering`	No
`sortedBy`	No
`timeZone`	No
`countries`	No
`keyEvents`	No
`siteScope`	No
`sortOrder`	No
`thenOrder`	No
`dataSource`	No
`isKeyEvent`	No
`metricMode`	No
`propertyId`	No
`prevSummary`	No
`currencyCode`	No
`emptyBecause`	No
`landingPages`	No
`methodLimits`	No
`hasComparison`	No
`keyEventNames`	No
`notConfigured`	No
`rawEventCount`	No
`reauthRequired`	No
`comparisonRange`	No
`prevRawEventCount`	No
`propertyDisplayName`	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"
+}

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

Changed3 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 / metricMode

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

addedOutput schema / properties / reauthRequired

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

Changed2 schema fields changedOct 8, 2026

addedOutput schema / properties / prevRawEventCount

Added value: +{
+  "$ref": "#/properties/range/anyOf/0/properties/days"
+}

addedOutput schema / properties / rawEventCount

Added value: +{
+  "$ref": "#/properties/range/anyOf/0/properties/days"
+}

Changed5 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 / isKeyEvent

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

addedOutput schema / properties / keyEventNames / $ref

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

removedOutput schema / properties / keyEventNames / anyOf

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

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.6/5.0

Behavior4/5

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

Adds substantial behavior beyond the readOnly/destructive annotations: auto-selection of the most active key event, isKeyEvent:false fallback for plain events, event_filter metricMode for names with special characters, rawEventCount gap notes, rates as 0-1 fractions, notConfigured state, and ~2-3 day data lag. Only minor gap is that it does not describe response shape for the automatic period selection beyond the default window.

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 primary alternative before edge cases, and every sentence carries operative information. It is dense and long, bundling many fallback behaviors, but little is redundant.

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?

With 8 params, nested filters, and an output schema present, the description supplies exactly the missing operational context: defaults, fallback modes, rate semantics, and the notConfigured state. An agent has what it needs to invoke correctly.

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 88%, so the baseline is 3. The description adds real semantic value on keyEvent omission (auto-pick with available names returned), the default 28-day window when dates are omitted, and the meaning of rate fields, going beyond 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 and resource (segments GA4 key events/conversions) and enumerates the breakdowns returned. It explicitly separates itself from get_ga4_ecommerce, so an agent can route 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 many conversions... and which channels, pages or devices drove them" gives a concrete trigger, and "Not for revenue or products: use get_ga4_ecommerce" names the alternative and the exclusion. Omission behavior for keyEvent and dates is also specified.

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?