SEO GSC Wizard MCP

Product free-listing status

get_product_listing_status

Read-only

Use this when the user asks which products are missing from free listings, and why. Free-listing eligibility and item issues per product, from the Google Merchant Center account linked to a GSC Wizard site, sorted by clickPotentialRank (1 = the product Google expects the most clicks from; unranked products last, ties by offerId). Each row carries the aggregated status (ELIGIBLE / ELIGIBLE_LIMITED / PENDING / NOT_ELIGIBLE_OR_DISAPPROVED), the free-listings status when the synced catalog has it, the top issue code and whether fixing it needs a merchant action or is just pending Google processing. statusCounts, issueCounts (the 20 most common top issues, most frequent first), problemCount and merchantActionCount (problems that need a feed or site fix) summarise the whole scan, not just the returned page; page through every row with offset, passing back nextOffset until it is null. Answered from the catalog snapshot GSC Wizard syncs daily into its warehouse when the site has one (dataSource: "clickhouse", syncedAt says when, stale: true when it is more than two days old; every offer is counted), with a live Merchant API scan of up to 5,000 products as the fallback (dataSource: "merchant-api", truncated when the catalog had more or Merchant Center was too slow to read it all within about 40 seconds; truncationReason says which). itemIssuesUnavailable: true means Google refused the issue data, so a missing issue code is unknown rather than clean. syncPaused (with a one-line staleNote) means the daily sync is paused because Merchant Center no longer lets the connected Google account read the merchant: the data is still returned but may be stale, and syncPaused.message says how to fix it. syncNotice (reason "gmc_on_other_account") means Merchant Center is connected on another Google login than the property's Search Console one, so the snapshot cannot refresh; the data is still returned. This is catalog state, not traffic. Not for the clicks a product actually got: use get_organic_shopping_performance. Returns a notConfigured result (not an error) when Merchant Center is not connected, its credentials were revoked, no Merchant Center account is linked to the site in the GSC Wizard app, or (reason "gmc_on_other_account") nothing was ever synced because Merchant Center sits on another Google login and no live read is possible.

Input Schema

Name	Required	Description
`limit`	No	Product rows to return, highest click potential first (default 25, max 200).
`offset`	No	Rows to skip, for reading past the first page: pass the previous answer's nextOffset (default 0, max 100,000).
`siteUrl`	Yes	The property URL as returned by list_sites (e.g. "sc-domain:example.com").
`onlyProblems`	No	Return only products that are not plainly serving (limited, pending, disapproved, or carrying an item issue). Set false to list the whole catalog by click potential.

Output Schema

Name	Required	Description
`hint`	No
`note`	No
`rows`	No
`range`	No
`stale`	No
`offset`	No
`reason`	No
`thenBy`	No
`account`	No
`hasMore`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`scanned`	No
`siteUrl`	No
`cachedAt`	No
`nextStep`	No
`ordering`	No
`rowCount`	No
`sortedBy`	No
`syncedAt`	No
`sortOrder`	No
`staleNote`	No
`thenOrder`	No
`truncated`	No
`dataSource`	No
`nextOffset`	No
`syncNotice`	No
`syncPaused`	No
`issueCounts`	No
`emptyBecause`	No
`gmcAccountId`	No
`methodLimits`	No
`onlyProblems`	No
`problemCount`	No
`statusCounts`	No
`notConfigured`	No
`itemIssuesNote`	No
`truncationNote`	No
`truncationReason`	No
`merchantActionCount`	No
`itemIssuesUnavailable`	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."
+}

Changed17 schema fields changedOct 18, 2026

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

addedOutput schema / properties / emptyBecause

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

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

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 / rows / items / additionalProperties
```
Previous value: -falseNew value: +true
```
addedOutput schema / properties / rows / items / properties / contentLanguage
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```
addedOutput schema / properties / rows / items / properties / feedLabel
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```
addedOutput schema / properties / rows / items / properties / productId
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```

addedOutput schema / properties / sortOrder

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

addedOutput schema / properties / sortedBy

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

changedOutput schema / properties / syncNotice / anyOf

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

changedOutput schema / properties / syncPaused / anyOf

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

addedOutput schema / properties / thenBy

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

addedOutput schema / properties / thenOrder

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

Changed2 schema fields changedOct 10, 2026

addedOutput schema / properties / syncNotice

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

addedOutput schema / properties / syncPaused

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

Changed4 schema fields changedOct 10, 2026

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Rows to skip, for reading past the first page: pass the previous answer's nextOffset (default 0, max 100,000).",
+  "maximum": 100000,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / merchantActionCount

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

addedOutput schema / properties / nextOffset

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

addedOutput schema / properties / offset

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

Changed8 schema fields changedOct 10, 2026

addedOutput schema / properties / cachedAt

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

addedOutput schema / properties / itemIssuesNote

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

addedOutput schema / properties / itemIssuesUnavailable

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

addedOutput schema / properties / rows / items / properties / freeListingsStatus
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```

addedOutput schema / properties / stale

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

addedOutput schema / properties / staleNote

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

addedOutput schema / properties / syncedAt

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

addedOutput schema / properties / truncationReason

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

First observedOct 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Goes well beyond the readOnly/openWorld annotations: it discloses the two data sources (daily ClickHouse snapshot vs. live Merchant API capped at 5,000 products / ~40s), staleness rules (>2 days = stale), truncation reasons, and degraded states (itemIssuesUnavailable, syncPaused, syncNotice). The one gap is that it never explains the cost/latency tradeoff of the live fallback beyond the 40s note, but the behavioral surface is unusually well covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded correctly with the usage trigger and the key sorting rule, and most sentences carry distinct edge-case information. However it is one dense ~350-word block with no breaks between data-source, staleness, truncation, and sync-state concerns, 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?

Given an output schema exists, return values need not be explained, yet the description still names the summary fields (statusCounts, issueCounts, problemCount, merchantActionCount) and clarifies they cover the whole scan rather than the page — exactly the kind of subtlety an agent would otherwise get wrong. Every non-obvious state (notConfigured, truncated, syncPaused) is accounted for.

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%, so the baseline is 3; the description still adds value by explaining pagination intent ('page through every row with offset, passing back nextOffset until it is null') and the clickPotentialRank ordering that governs limit/offset. onlyProblems semantics are left entirely to the schema, which is acceptable given full coverage.

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 ('free-listing eligibility and item issues per product') and immediately scopes it to the Merchant Center account linked to a GSC Wizard site. It explicitly distinguishes itself from the nearest sibling by declaring 'This is catalog state, not traffic' and naming get_organic_shopping_performance as the traffic alternative.

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 an explicit trigger ('Use this when the user asks which products are missing from free listings, and why') and closes with an explicit exclusion plus the correct alternative ('Not for the clicks a product actually got: use get_organic_shopping_performance'). The notConfigured cases further tell the agent what a non-error empty answer means.

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?