Skip to main content
Glama
MoonEyes

google-ecommerce-mcp

by MoonEyes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Merchant Center product issues

merchant_product_issues
Read-onlyIdempotent

Identify Google Merchant Center product disapprovals, demotions, and warnings across destinations. Scans pages to return issues with the attribute to fix.

Instructions

Merchant Center products with their item-level issues (disapprovals, demotions, warnings) per destination, with the attribute to fix. Scans every page of products up to max_pages. Returns {"products": [{offer_id, feed_label, title, link, issues: [{code, severity, description, attribute, destination}]}], "scanned": n, "truncated": bool}.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum products returned (1 to 1000)
client_idNoClient id from clients_list. Required when several clients are registered; empty uses the only client (or the environment variables when there is no client registry)
max_pagesNoPages of 250 products to scan at most
only_with_issuesNoTrue: only products with at least one issue; False: every product

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / client_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Client id from clients_list. Required when several clients are registered; empty uses the only client (or the environment variables when there is no client registry)",
+  "title": "Client Id"
+}
  2. Changed7 schema fields changedv0.1.2
    • addedInput schema / properties / limit / description
      Added value: +"Maximum products returned (1 to 1000)"
    • addedInput schema / properties / limit / maximum
      Added value: +1000
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / max_pages / description
      Added value: +"Pages of 250 products to scan at most"
    • addedInput schema / properties / max_pages / maximum
      Added value: +200
    • addedInput schema / properties / max_pages / minimum
      Added value: +1
    • addedInput schema / properties / only_with_issues / description
      Added value: +"True: only products with at least one issue; False: every product"
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the bar is lower. The description still adds real behavioral context: it scans every page of products up to max_pages, so unbounded-ish work is disclosed, and it explains the truncation semantics via the returned 'truncated' flag.

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?

Two dense sentences with the purpose front-loaded and the return shape compactly inlined as a literal JSON sketch. No filler or hedging; only minor cost is the somewhat cramped embedded schema notation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries return-value burden and does so by enumerating the product and issue fields (offer_id, feed_label, title, link, code, severity, attribute, destination) plus scanned/truncated. Combined with annotations covering the safety profile, this is nearly complete; only the routing against account-level and patch siblings is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents limit, max_pages, only_with_issues and client_id thoroughly. The description only echoes max_pages scoping and the return shape; it adds no format or interaction detail (e.g. how limit interacts with the 'scanned' count) beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it retrieves Merchant Center products together with their item-level issues (disapprovals, demotions, warnings) broken out per destination and the attribute to fix. This clearly distinguishes it in spirit from account-level issue tools, but it never names the sibling it differs from (e.g. merchant_account_issues or merchant_products), so the differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the item-level diagnostic scan and that merchant_plan_product_patch would follow to fix the returned attributes, but the description never says when to choose this over merchant_account_issues or when a plain merchant_products listing would suffice. No exclusions or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools