MCP
Orders tools
MCP tools for orders: what each does, the key level it needs, the operation it runs and its input schema. Part of the MISSIN public API: call it with an API…
An operation tool runs one API operation and takes its variables, so the operation's page says what each accepts. Two differences: the server fills in workspaceId and updatedBy, and campaignId, partnerId, formId, discountCodeId, socialNetworkId, waitlistId, incentiveId, channelId also take the record's name. A task tool chains several operations and is described here in full. Every tool's input schema, keyed by tool name: orders.schema.json.
Operation tools
| Tool | Operation | Access | Toolset | Hints | What it does |
|---|---|---|---|---|---|
list_checkouts | CheckoutsList | Read | orders | read-only, idempotent | Page through storefront checkouts with a condition and sort. |
get_checkouts_summary | CheckoutsSummary | Read | orders | read-only, idempotent | Checkout totals: started versus completed, for the conversion rate. |
list_orders | OrdersList | Read | core | read-only, idempotent | Page through orders with filter and sort: totals, discount, partner and attribution. |