The AI Assistant can only perform a fixed, known set of actions — called tools. It cannot run arbitrary commands, read unrelated data, or change anything outside shipment tracking. Every tool runs as the store account the assistant signed in with, so it can never do more than that account could do by hand.
On the Connection URL route, tools are scoped to tracking only — no refunds, prices, or payment details. On the WooCommerce MCP route, the AI also has access to WooCommerce’s own order, product, and customer tools.
Tracking tools
| Tool | Type | Parameters | Returns | Example prompt |
|---|---|---|---|---|
get-tracking | Read | order_id (required) | Array of tracking entries for the order — carrier, tracking number, tracking link, and shipped date. Empty array if no tracking is recorded. | “What’s the tracking on order #1234?” |
get-orders-missing-tracking | Read | None — returns all unfulfilled orders with no tracking | List of orders with order number, status, date placed, customer name, and shipping country. | “Which orders are missing tracking?” or “Show me unfulfilled orders.” |
get-shipments | Read | carrier (optional, display name); date_from / date_to (optional, YYYY-MM-DD) | List of orders that have tracking, with totals by carrier. Narrowable to a single carrier or a date range. | “How many orders went out by FedEx last month?” or “What shipped between 1 June and 30 June?” |
add-tracking | Write | order_id (required); tracking_number (required); carrier (required, display name matching an enabled carrier or API alias) | Confirmation that tracking was added, or an error message. | “Add USPS tracking 9400110200793935305128 to order #1230.” |
delete-tracking | Delete | order_id (required); tracking_number (required to identify which entry to remove) | Confirmation that the entry was removed, or an error message. | “Remove the FedEx tracking from order #1229.” |
Error behaviour
- Order not found —
get-tracking,add-tracking, anddelete-trackingreturn an error if the order ID does not exist. The assistant surfaces the error in chat. - Carrier not recognised —
add-trackingvalidates the carrier name against your enabled carriers and configured API aliases. If it does not match, the call fails with a carrier-not-found error. Set up an API alias to map the name your AI uses to the correct carrier. - Tracking already present — adding a duplicate tracking number to the same order returns an error if Restrict adding the same tracking number is enabled in Shipment Tracking API Settings.
- Write access off — if Allow the AI to add and delete tracking is disabled,
add-trackinganddelete-trackingare not offered on the Connection URL route and calls to them return a permission error. - Delete matches zero or multiple entries — if no tracking number matching the request is found on the order,
delete-trackingreturns an error. If the order has multiple tracking entries, the assistant identifies the correct one by tracking number — always specify it.
Built-in safety
- Same rules as adding tracking by hand — carrier validation, order status changes, and customer emails all follow your AST PRO settings. The AI cannot skip them.
- Read-only when you want it — turn off Allow the AI to add and delete tracking in Enable & Configure and the write tools are no longer offered.
- Logged — every call is written to the Audit Log with the tool name, channel, app, user, and result.