Manage one storefront: listings, bulk catalogue sync, analytics and webhooks.
Scored across 15 tools
Most tools map cleanly to a resource+action (get_listing vs list_listings vs update_listing; delete_listing vs delete_webhook). The only real overlap is the batch trio: create_listing, bulk_create_listings, and sync_catalogue all create listings, and an agent must read carefully to know that sync upserts by externalId with partial/full retirement semantics. update_listing vs set_listing_status is borderline but the descriptions delineate them.
Strong verb_noun snake_case pattern: create_listing, get_listing, list_listings, update_listing, delete_listing, register_webhook, sync_catalogue. The analytics_listings/analytics_summary pair uses a resource-first namespace rather than a verb, which is a minor deviation but still readable and predictable.
15 tools is well within the ideal range and each one earns its place: full listing lifecycle, batching, analytics, webhooks, and shop profile. Nothing feels padded or redundant given the batch/sync distinction.
Listings CRUD, status, bulk/sync, analytics, webhooks, and shop profile are covered, but the surface stops at lead counts — there is no tool to read individual leads or inquiries, which is a core marketplace workflow. Also missing a get_webhook/single-webhook read and any delivery-retry operation, so agents may hit dead ends outside catalogue management.
Per-listing daily views + leads (deltas) over a date range, plus totals. Keyset-paginated.
Inputs: to, from, limit, cursor.
Shop-level totals: views, leads, and listing counts by status.
Inputs: no named parameters.
Create up to 200 listings in one call. Each is independent; image URLs are re-hosted.
Inputs: listings (required).
Create a listing. Image URLs may be public — they are re-hosted to first-party storage automatically.
Inputs: title (required), categorySlug (required), brand, model, +8 more.
Delete one of the shop's listings. While the shop or the listing is under investigation (an open report, or the account is held/suspended) it is hidden instead — the result then says deleted: false, hidden: true and why.
Inputs: id (required).
Unregister a webhook endpoint by id.
Inputs: id (required).
Get one of the shop's listings by id (any status).
Inputs: id (required).
Get the authenticated shop's storefront profile, trust score, and live listing count.
Inputs: no named parameters.
List the shop's listings (all statuses). Keyset-paginated — pass the returned next_cursor to page.
Inputs: limit, cursor, status.
List the shop's registered webhook endpoints (secrets are never returned) with delivery health.
Inputs: no named parameters.
Register an HTTPS endpoint for signed listing events. The signing secret is returned ONCE — store it.
Inputs: url (required), events.
Set a listing's availability: active | sold | hidden. Re-activating a listing that is waiting for eno's licence check is refused with licence_check_required until eno approves it.
Inputs: id (required), status (required).
Upsert the catalogue by your own externalId. mode "partial" only touches sent rows; "full" also retires listings absent from the payload. Up to 200 rows.
Inputs: listings (required), mode.
Edit one of the shop's listings (sparse). Image URLs may be public — re-hosted automatically. A job's pay is salaryM; a price sent for a job is read as its monthly salary in VND. An edit of a listing that is waiting for eno's licence check answers held: true: the listing stays unpublished until eno approves it (this tool cannot change a subcategory or the licence values).
Inputs: id (required), price, title, images, +4 more.
Edit the storefront profile. Sparse — only the fields you send change.
Inputs: bio, name, phone, location, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Manage a Hyprcart store: catalog, prices, stock, orders and content, with the merchant's consent.
Read and manage Sign Customiser stores: customisers, options, pricing, products and orders.
Run storefronts, listings, orders, content, fulfillment, and analytics through AI.
Manage products, orders, customers, inventory, and store configuration
Add one secure layer between your agents and this server.
