Get the plugin
WP MCP/Documentation/WooCommerce Tools

WooCommerce Tools

wpmcp treats a WooCommerce store as a first-class surface, not an afterthought bolted onto the content tools. An AI agent can read products, orders, and sales data, and make the day-to-day changes a shop owner actually asks for: updating a price, marking an order as shipped, adjusting stock. Every one of those changes goes through the same snapshot/rollback engine documented in The safety model, so a bad price edit or a wrong order-status change is a one-click undo, not a support ticket.

What a shop owner gets

  • Read the whole store. list-products and get-product for the catalog, list-product-categories for how it is organized, list-orders and get-order for what customers have bought, get-sales-report for a date-range summary of gross sales, order count, items sold, and top products by quantity.
  • Change products safely. update-product edits price, stock, description, SKU, and status. A product is a WordPress post under the hood, so the change is snapshotted the same way an ordinary page edit is: rollback-operation puts the exact prior price and stock quantity back, not an approximation.
  • Change order status safely. update-order-status moves an order through the store’s registered statuses (processing, completed, refunded, and so on), validated against what the store actually supports. It is snapshotted via a dedicated wc_order object type, so rollback-operation restores the prior status exactly, whether the store uses WooCommerce’s classic post-based orders or the newer High-Performance Order Storage (HPOS) tables. Every order tool is HPOS- and CPT-safe: it does not assume one storage backend, so the same tools work whether or not a store has migrated to HPOS.
  • Create products, and add order notes. create-product and add-order-note are additive: a new product with no prior state to snapshot, or a note appended to an order’s history. A mistaken product is removed with delete-product.
  • Variations, coupons and tax rates. list-variations, create-variation, update-variation and delete-variation; list-coupons, get-coupon, create-coupon, update-coupon, validate-coupon and delete-coupon; list-tax-rates, create-tax-rate, update-tax-rate and delete-tax-rate. Bulk price and stock passes go through bulk-update-products, and list-low-stock-products finds what needs reordering.

Product import in two steps

plan-product-import is read-only: it validates every row, matches it to an existing product by SKU, and returns a plan in which each row is a create, an update (with a field-level diff), a skip (with a reason) or an error (with every problem found). Nothing is written, no image is fetched, and category and attribute terms must already exist. The plan carries a hash of the rows, the plan and the current state of every matched product.

apply-product-import writes exactly that plan. It rebuilds the plan first and refuses if anything moved in between (a matched product edited, a SKU taken, a category removed), refuses a plan with error rows, and needs confirm: true above its product threshold. Writes go through the same paths as the single-product tools, image URLs go through the guarded remote media download, and everything shares one session_id, so rollback-session undoes the whole import. A row that fails part way rolls back the whole session: an import is all or nothing. Both steps are free.

The Pro operations catalog

WP MCP Pro adds three abilities that reach much more of the store without adding a tool per endpoint: woo-ops lists the catalog (every op with its mode, route, capability, whether it needs confirm: true, and which snapshot backs it), woo-read runs read ops, and woo-write runs write and destructive ops, singly or as a batch under one session_id. Ops are named by domain, for example orders.update or shipping.add-method.

  • Orders. orders.create and orders.update run through WooCommerce’s order CRUD, so HPOS and the legacy post store both work. No payment gateway is ever called: set_paid and transaction_id are refused, and the payment method is a plain label. An edit is snapshotted as the full order and rolls back exactly; a create is rolled back by trashing the order. Responses leave out order meta, the transaction id, and the customer IP and user agent.
  • Shipping. Zones (shipping.create-zone, shipping.update-zone, shipping.delete-zone) and the three core methods, flat rate, free shipping and local pickup (shipping.add-method, shipping.update-method, shipping.remove-method), validated field by field against each method’s own settings form. Every write except a zone create is snapshotted as the whole zone; a create’s rollback deletes the zone, and only while it is still the zone that was created. Third-party methods are listed without their settings, which can hold carrier credentials.
  • Webhooks. webhooks.create, webhooks.update, webhooks.pause and webhooks.delete. The signing secret is write-only and masked in every response, the delivery URL must be a public https address that passes an SSRF guard, custom action.* topics are refused, and a webhook always delivers as the user who made it.
  • Payment gateways. gateways.list and gateways.get mask every key, secret, password, token, signature or credential field and every password-type field. gateways.update changes the enabled flag, title, description, order and non-secret settings, and refuses secret fields outright: the store admin screen stays the place to set a credential. Each write is snapshotted as the one option it changes, and restoring it takes manage_woocommerce, because the snapshot holds the gateway’s secrets.
  • Reviews. reviews.list (never the reviewer’s email or IP), reviews.approve, reviews.unapprove, reviews.spam, reviews.update, reviews.reply and reviews.trash. Every review op needs moderate_comments plus edit_product on the review’s product. Each change is snapshotted as the full comment with its rating and verified flag; a reply’s rollback trashes it.
  • Reports. reports.sales (optionally by day, week or month), reports.top-sellers, reports.orders, reports.customers and reports.coupons, from WooCommerce’s analytics tables when they agree with the order store and from order queries otherwise. Aggregate figures only, never a customer’s name, email or address.
  • System status. system-status.get reads the status report by section with secret-like values masked; system-status.tools lists the maintenance tools; system-status.run-tool runs an allowlisted one (clearing transients, regenerating lookup tables and similar). Tools that delete store rows need confirm: true, and every run says why it cannot be rolled back.
  • Brands. brands.list, brands.get, brands.create, brands.update, brands.delete, brands.assign and brands.unassign, available when the store registers the brands taxonomy.
  • Everything else in the catalog: products, variations, coupons, customers, refunds, tax rates and classes, and store settings through the store’s own wc/v3 routes.

What is honestly not undoable: refunds.create is snapshotted but reports recoverable: false (the order status comes back, the money does not), status tools rebuild derived data and are not snapshotted, and plain creates report the op that removes what they made. Destructive ops are off until a site opts in with the wpmcp_woo_op_enabled filter and always need confirm: true.

The one-click undo, and why it matters here specifically

Most AI-for-WooCommerce integrations either refuse to touch products and orders at all, or let an agent write directly with no way back. That is a real risk on a live store: an agent that fat-fingers a price from $49 to $4.90, or flips a paid order to “refunded” by mistake, has just cost real money in the minutes before a human notices.

wpmcp’s answer is the same safety engine used everywhere else in the plugin:

  1. update-product and update-order-status snapshot the object before the change applies.
  2. The change happens.
  3. If it turns out to be wrong, rollback-operation (from the agent, or a one-click Restore button on the wpmcp wp-admin screen) restores the exact prior state: the old price, the old stock count, the old order status.

This is the detail worth underlining for anyone evaluating AI tools against a live store: product and order-status changes are undoable by construction, not by promise. A tool that writes through direct database or REST access with no snapshot in the write path leaves no undo once a write lands; recovering means restoring from a nightly backup (losing every order placed since), or fixing it by hand from memory. wpmcp’s snapshot happens at the moment of the change, so the fix is a single click, seconds later, with no data loss for anything else that happened on the store in between.

Destructive and disabled-by-default tools

  • delete-product is disabled by default (a site must opt in via the wpmcp_enable_delete_product filter) and always requires confirm: true. Trash is the default path; force: true permanently deletes, and even that is snapshotted, a force-deleted product resurrects at its original ID with its price, stock, and category terms intact.

Capabilities

Read tools (list-products, get-product, list-product-categories, get-sales-report) and product writes require manage_woocommerce, matching WooCommerce’s own admin gate. Order tools (list-orders, get-order, update-order-status, add-order-note) require edit_shop_orders. The Pro catalog checks a capability per op before dispatch and is never looser than the free tool covering the same data: order, note and refund reads keep edit_shop_orders, customer reads need list_users and customer writes edit_users or create_users, review ops need moderate_comments plus edit_product, and everything else needs manage_woocommerce. The store endpoint’s own permission check still runs on top. It defers to the store’s existing WooCommerce roles, so a shop owner does not need to reason about a second permissions model.

See the Tools reference for the full argument-level detail on every WooCommerce tool.

Previous: Free vs ProNext: Contributing and TestsAll documentation