Catalog keeps a store’s approved product specs, the price the store allows an assistant to state, and availability, then lets an assistant read that catalog before it writes. A 14-day trial, then Pro. The price is only at checkout.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 5 tools
Each tool has a distinct purpose: listing stores, creating a store, retrieving a catalog, saving a product, and validating shopping copy. There is no meaningful overlap between retrieval, mutation, and validation operations. An agent can clearly choose the right tool for each step.
All tool names use snake_case with a verb-noun structure: check_shopping_copy, create_store, get_store_catalog, list_stores, save_product. The pattern is predictable and readable, with only minor length variation. Verb choices are appropriate for their actions.
Five tools is well-scoped for a catalog and store management server. Each tool covers a necessary part of the workflow without redundancy. The surface is neither too thin nor bloated.
Core lifecycle operations are covered: store creation and listing, catalog retrieval, product upsert/retirement, and draft validation. Minor gaps remain, such as explicit update or delete operations for stores. These are workaroundable but could limit some store-management workflows.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
check_shopping_copycreate_storeget_store_cataloglist_storessave_product
Add one secure layer between your agents and this server.