No user-submitted related servers found.
Scored across 29 tools
The typed per-resource tools (create_product, update_order, search, get) are distinct, but the generic escape hatches overlap heavily: shopify_run_action, shopify_graphql_mutation, shopify_graphql_query, and shopify_graphql_query_many all run arbitrary GraphQL, and shopify_get/search/report also read data. Descriptions do draw boundaries (run_action=multi-store any mutation, graphql_mutation=single store, graphql_query=read-only), so an attentive agent can choose, but the surface is confusable.
Every tool carries the shopify_ prefix in snake_case with a mostly predictable verb_noun pattern (shopify_create_product, shopify_update_order, shopify_list_stores, shopify_search). A few deviate to noun-only forms (shopify_metafields, shopify_redirects, shopify_tags), and the graphql_* cluster differs, but overall it is highly readable and consistent.
29 tools is on the heavy side, though the scope (the full Shopify Admin API across multiple stores) partly justifies it and the find/describe/run pipeline generalizes away hundreds of mutations. A few entries (e.g. graphql_query vs graphql_query_many, run_action vs graphql_mutation) could be consolidated, making it somewhat over-provisioned.
The surface covers the core commerce lifecycle (products, collections, orders, customers, inventory, discounts, fulfillments, metafields, redirects, tags) plus a rich reporting layer and read/search tools. Crucially, shopify_run_action with find/describe provides a universal escape hatch for any mutation not covered directly, leaving no real dead ends.