No user-submitted related servers found.
Scored across 129 tools
The tools cover many distinct domains (designs, products, stores, orders, fulfillment, channels, analytics, workspaces), and the descriptions often explicitly route between overlapping options. However, with 129 tools there are many near-neighbors—create_product vs ship_product vs design_apparel, generate_image vs generate_listing_image, sync_to_channel vs import_channel_catalog vs bind_tracked_listing, and several analytics/channel tools—so misselection remains likely despite the detailed guidance.
Nearly all tools use consistent snake_case, and most follow a verb_noun pattern such as list_my_stores, create_product, sync_to_channel, and update_store_settings. There are minor deviations: several analytics/channel tools are noun-first (analytics_summary, channel_performance, listing_changes), and a few names use less standard verbs (ship_product, design_apparel), but the convention is still broadly predictable.
129 tools is far beyond a practical MCP surface and is an extreme mismatch even for a broad apparel/e-commerce platform. The count forces agents to navigate a very large decision space and makes tool selection, documentation overload, and accidental misuse major risks.
The tool surface covers the apparent domain extensively: design generation/upload/archive/delete, product creation/variants/pricing/sync/archive, collections, stores, orders, fulfillment issues, channel listing attributes and performance, workspaces, members, and analytics. Obvious lifecycle alternatives such as archive vs delete are present, and the escape-hatch api_request plus get_api_reference fills residual gaps.