No user-submitted related servers found.
Scored across 22 tools
Each tool targets a clear resource+action pair with distinct boundaries, and the CRUD groups for products, data sources, and promotions are cleanly separated. The only area of potential confusion is search_reports versus the two price_* tools, which are thin wrappers over canned MCQL queries — though the descriptions explicitly position them as such. Similarly, get_product (per-product issues) and list_product_issues (aggregate) are cross-referenced to prevent misselection.
Most tools follow a clean verb_noun convention (list_*, get_*, insert_*, update_*, delete_*), but there are notable inconsistencies: product and promotion creation uses insert_ while data sources use create_ (create_data_source), the price_competitiveness and price_insights tools drop the verb entirely, and raw_request breaks pattern. The dominant convention is readable and predictable, but the mixed creation verbs (insert_ vs create_) create genuine ambiguity about which to use for a new operation.
At 22 tools this sits at the high end of the ideal range, but the count is well-justified by the breadth of the Google Merchant domain — accounts, products, data sources, promotions, reporting, issues, and quotas are all distinct subdomains. The inclusion of a raw_request escape hatch is a thoughtful alternative to ballooning the surface area with dozens more niche tools for rarely used operations.
The core product workflow is fully covered: full CRUD for product inputs, sufficient data source management to support writes, promotion create/read, robust reporting and insights, and aggregate issue visibility. The most notable gaps — no delete_promotion, no update/delete for data sources, and read-only homepage/shipping settings — are explicitly called out in descriptions, and the raw_request tool provides a safe fallback for those long-tail operations rather than leaving agents in a dead end.