Skip to main content
Glama
MoonEyes

google-ecommerce-mcp

Plan a Merchant Center product change

merchant_plan_product_patch
Read-only

Plan attribute changes, such as title, description, link, availability, or price, for one Merchant Center product before applying them.

Instructions

PLAN (nothing is written): change some attributes of one product of the client's Merchant Center account, with an explicit update mask (an attribute listed without a value is refused: Google would delete it). Title and description are low risk, link and availability medium, price high and financial (needs a human approval; capped by write.merchant.max_daily_budget_micros, max_increase_pct and cap_currency). Only API data sources. Apply with google_apply after the user agreed; changes show after up to 30 minutes; rollback_plan restores the previous values. Product insert, delete and inventories are deliberately not offered.

Input Schema

NameRequiredDescriptionDefault
client_idNoClient id from clients_list. Required when several clients are registered; empty uses the only client
account_idNoMerchant Center account id of the client (empty: the configured one)
product_idYesProduct id contentLanguage~feedLabel~offerId, as merchant_products returns it (e.g. en~FR~SKU123)
update_maskYesAttributes to change, each also given in product_attributes: title, description, link, availability, price
data_source_idNoNumeric id of the API data source to patch (empty: the product's primary data source)
product_attributesYesNew values, e.g. {"title": "...", "availability": "OUT_OF_STOCK", "price": {"amount_micros": 12990000, "currency_code": "EUR"}}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare safety hints; the description adds rich behavior beyond them: risk tiers per attribute (title/description low, link/availability medium, price high), human approval requirement for price, budget caps (write.merchant.max_daily_budget_micros, max_increase_pct, cap_currency), the ~30-minute propagation delay, and rollback via rollback_plan. Nothing is written — consistent with readOnlyHint=true.

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?

Every clause carries information (risk tiers, caps, timing, exclusions) with the plan-only constraint front-loaded in capitals. It is dense and somewhat run-on, but no sentence is filler.

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?

For a mutating-adjacent planning tool with no output schema, the description covers the write path, approval gates, budget caps, latency, rollback, and explicit non-capabilities. An agent has everything needed to plan and then hand off to google_apply.

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 description coverage is 100%, so the baseline is 3, but the description adds a genuine semantic rule for update_mask: 'an attribute listed without a value is refused: Google would delete it.' That constraint is not derivable from the schema and prevents a destructive mistake.

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 ('PLAN (nothing is written): change some attributes of one product of the client's Merchant Center account') and distinguishes itself from siblings like merchant_products by emphasizing the plan-only nature. An agent can tell exactly what this does without opening the 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?

Explicitly routes to the apply step ('Apply with google_apply after the user agreed') and states exclusions ('Product insert, delete and inventories are deliberately not offered'). This is the when/when-not/alternatives pattern at full strength.

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