SEO GSC Wizard MCP

List GA4 properties

list_ga4_properties

Read-only

Use this when the user asks which Google Analytics 4 properties they can read, needs a GA4 property ID, or wants to check which GA4 property a site is linked to. Lists every GA4 property readable by the connected Google accounts of the authenticated user, and which GSC Wizard sites each property is linked to (via linkedSiteUrls), sorted by displayName, A to Z. Not for Search Console properties: use list_sites. linkedSiteUrls covers only the sites of the GSC Wizard account this connection is authenticated as (returned as account): links made from a different GSC Wizard account come back empty here even though the app shows them. An empty result with connected: false means the Google Analytics consent has not been granted in the GSC Wizard app yet (connect Google Analytics at tool.gscwizard.com first), or, with reauthRequired: true, that it was granted but Google now rejects every such account, so it has to be reconnected. errors lists every Google account whose properties could not be read (its properties are missing from the list), with the reason.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`hint`	No
`note`	No
`count`	No
`error`	No
`errors`	No
`thenBy`	No
`account`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`nextStep`	No
`ordering`	No
`sortedBy`	No
`connected`	No
`sortOrder`	No
`thenOrder`	No
`properties`	No
`emptyBecause`	No
`methodLimits`	No
`reauthRequired`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / listKey

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

Changed11 schema fields changedOct 18, 2026

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

addedOutput schema / properties / emptyBecause

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

changedOutput schema / properties / errors / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "accountEmail": {
-          "$ref": "#/properties/hint"
-        },
-        "message": {
-          "$ref": "#/properties/hint"
-        },
-        "reason": {
-          "$ref": "#/properties/hint"
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "accountEmail": {
+          "$ref": "#/properties/hint"
+        },
+        "message": {
+          "$ref": "#/properties/hint"
+        },
+        "reason": {
+          "$ref": "#/properties/hint"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / methodLimits

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

addedOutput schema / properties / nextStep

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

addedOutput schema / properties / ordering

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

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

addedOutput schema / properties / sortOrder

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

addedOutput schema / properties / sortedBy

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

addedOutput schema / properties / thenBy

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

addedOutput schema / properties / thenOrder

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

Changed2 schema fields changedOct 10, 2026

addedOutput schema / properties / errors

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "accountEmail": {
+            "$ref": "#/properties/hint"
+          },
+          "message": {
+            "$ref": "#/properties/hint"
+          },
+          "reason": {
+            "$ref": "#/properties/hint"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / reauthRequired

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

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 past the readOnly/openWorld annotations: it discloses the A-to-Z sort order, the scoping limitation of `linkedSiteUrls` (only links from the authenticating GSC Wizard account, others appear empty), and the exact meaning of `connected: false` vs `reauthRequired: true` including the remediation step. It also explains that `errors` enumerates Google accounts whose properties are silently missing from the result — a subtle partial-failure mode an agent would otherwise misread as an empty list.

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 correctly: triggers first, then scope, then exclusion, then result semantics. It is on the long side for a zero-parameter list call, and since an output schema exists, some of the `linkedSiteUrls`/`errors` explanation partially duplicates structured data — but the connection-state caveats are non-obvious enough to earn their space.

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?

No input schema to speak of, but the description pre-empts every realistic failure interpretation: empty result vs missing consent vs revoked auth, and per-account read errors. Combined with the existing output schema and readOnly annotation, an agent has everything needed to call this and interpret the response 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?

Zero input parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description instead spends its detail on output-field semantics, which is beyond this dimension's scope but useful elsewhere.

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 (list every GA4 property readable by the connected Google accounts) and immediately differentiates from the nearest sibling: "Not for Search Console properties: use list_sites." An agent can distinguish it from list_ga4_custom_dimensions and other GA4 tools without opening any 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 three concrete trigger conditions (user asks which properties they can read, needs a property ID, wants to check which property a site links to) and then names the explicit exclusion and its alternative. Both when-to-use and when-not-to-use are covered.

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?