SEO GSC Wizard MCP

List Merchant Center accounts

list_gmc_accounts

Read-only

Use this when the user asks which Merchant Center accounts they can use, or which one a site is linked to. Lists every Google Merchant Center account readable by the connected Google accounts of the authenticated user, sorted by accountName, and which GSC Wizard sites each account is linked to (via linkedSiteUrls). Use it to discover the Merchant Center account id to link to a property, or to verify the Shopping setup of a site. Not for account issues or eligibility checks: use get_gmc_account_health. isAdvanced: true marks a multi-client parent account: reporting runs against a standalone account or one of its sub-accounts, never the parent itself. linkedSiteUrls covers only the sites of the GSC Wizard account this connection is authenticated as (returned as account). incomplete: true means the list is a floor, not the whole set: gaps and unprobedAccountIds say what could not be read or checked for sub-accounts, and errors names each connected Google account whose listing failed; retry for a complete list. An empty result with connected: false carries a reason: "no_scope" means the Merchant Center consent has not been granted in the GSC Wizard app yet (connect Merchant Center at tool.gscwizard.com first); "credentials_revoked" means it was granted but Google now rejects the stored credentials, so the Google account has to be reconnected on the Account page. On a shared property, linkedAccountId is withheld (null, with a note) until the owner enables the Merchant Center opt-in on your invite.

Input Schema

Name	Required	Description	Default
`siteUrl`	No	Optional property URL as returned by list_sites. When given, the response also reports which Merchant Center account is currently linked to that property (`linkedAccountId`).

Output Schema

Name	Required	Description
`gaps`	No
`hint`	No
`note`	No
`count`	No
`error`	No
`errors`	No
`reason`	No
`thenBy`	No
`account`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`siteUrl`	No
`accounts`	No
`nextStep`	No
`ordering`	No
`sortedBy`	No
`connected`	No
`sortOrder`	No
`thenOrder`	No
`incomplete`	No
`emptyBecause`	No
`methodLimits`	No
`incompleteNote`	No
`linkedAccountId`	No
`gcpProjectNumber`	No
`unprobedAccountIds`	No
`registrationRequired`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / listKey

Added value: +{
+  "$ref": "#/properties/reason",
+  "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
```
changedOutput schema / properties / accounts / items / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / emptyBecause

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

changedOutput schema / properties / errors / anyOf

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

addedOutput schema / properties / methodLimits

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

addedOutput schema / properties / nextStep

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

addedOutput schema / properties / ordering

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

addedOutput schema / properties / sortOrder

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

addedOutput schema / properties / sortedBy

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

addedOutput schema / properties / thenBy

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

addedOutput schema / properties / thenOrder

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

Changed18 schema fields changedOct 10, 2026

changedOutput schema / properties / account / $ref

Previous value: -"#/properties/hint"New value: +"#/properties/reason"

changedOutput schema / properties / accounts / items / properties / accountEmail / $ref
```
Previous value: -"#/properties/hint"New value: +"#/properties/reason"
```
changedOutput schema / properties / accounts / items / properties / accountId / $ref
```
Previous value: -"#/properties/hint"New value: +"#/properties/reason"
```
changedOutput schema / properties / accounts / items / properties / accountName / $ref
```
Previous value: -"#/properties/hint"New value: +"#/properties/reason"
```
changedOutput schema / properties / accounts / items / properties / name / $ref
```
Previous value: -"#/properties/hint"New value: +"#/properties/reason"
```

changedOutput schema / properties / error / $ref

Previous value: -"#/properties/hint"New value: +"#/properties/reason"

addedOutput schema / properties / errors

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

addedOutput schema / properties / gaps

Added value: +{
+  "$ref": "#/properties/accounts/items/properties/linkedSiteUrls"
+}

changedOutput schema / properties / gcpProjectNumber / $ref

Previous value: -"#/properties/hint"New value: +"#/properties/reason"

addedOutput schema / properties / hint / $ref
```
Added value: +"#/properties/reason"
```
removedOutput schema / properties / hint / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedOutput schema / properties / incomplete

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

addedOutput schema / properties / incompleteNote

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

changedOutput schema / properties / linkedAccountId / $ref

Previous value: -"#/properties/hint"New value: +"#/properties/reason"

changedOutput schema / properties / note / $ref

Previous value: -"#/properties/hint"New value: +"#/properties/reason"

addedOutput schema / properties / reason

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / siteUrl / $ref

Previous value: -"#/properties/hint"New value: +"#/properties/reason"

addedOutput schema / properties / unprobedAccountIds

Added value: +{
+  "$ref": "#/properties/accounts/items/properties/linkedSiteUrls"
+}

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 already cover read-only/no-destroy/open-world, yet the description adds substantial non-derivable behavior: sorting by accountName, the scope limitation of linkedSiteUrls to the authenticated GSC Wizard account, isAdvanced parent-vs-sub-account reporting rule, and partial-result semantics (incomplete/gaps/unprobedAccountIds/errors with retry advice).

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 purpose and use case, then progressive detail on edge cases and error codes. Dense and long, but nearly every sentence carries decision-relevant information; a few of the output-field explanations could be trimmed given the output schema exists.

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?

Covers everything an agent needs for a read-only discovery tool: when to call it, what the result means, how to react to empty/partial/failed results (reason codes and remediation), and permission-driven nulls. Behavior in failure modes is fully specified.

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 100% and the single optional siteUrl is fully documented there; the description reinforces its effect by noting linkedAccountId is only reported when a site is given and is withheld (null with a note) on shared properties. Minor added value over the schema, so a solid 4 rather than a 5.

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?

Opens with a specific verb and resource ('Lists every Google Merchant Center account readable by the connected Google accounts'), states the sort order, and names the sibling it is not for (get_gmc_account_health). An agent can distinguish it from get_gmc_account_info/list_sites 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?

Gives explicit trigger conditions ('when the user asks which Merchant Center accounts they can use, or which one a site is linked to'), two concrete use cases (finding the account id to link, verifying Shopping setup), and an explicit exclusion routing to get_gmc_account_health for issues/eligibility.

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?