WooCommerce Add-onTools Reference

WooCommerce Tools Reference

Reference for WooCommerce MCP tools provided by the Respira for WordPress WooCommerce Add-on (105 tools), grouped by products, orders, inventory, storefront, feeds, extensions, configurators, reports, store configuration, and webhooks.

How WooCommerce tools work with your AI assistant

WooCommerce tools let your AI assistant read and modify store data in a structured, auditable way. Each tool encapsulates a specific WooCommerce action such as listing products, updating orders, or checking stock.

Your AI assistant typically decides which tool to call based on natural language prompts. You do not need to remember every tool name, but knowing the main ones helps when you:

  • Design repeatable workflows and automations
  • Set guardrails for what the assistant is allowed to change
  • Review logs and audit which tools were used

When the WooCommerce add-on is installed, the assistant has access to 105 woocommerce_* tools (as of add-on v4.0.0) spanning products, variations and swatches, orders and refunds, coupons, customers, inventory, AI-readiness, storefront design intelligence, product feeds and llms.txt, cart links with agent-order attribution, Subscriptions, Bookings and Memberships, the STAGGS product configurator, bounded reporting, read-only store configuration, and approval-gated webhooks. That brings the total MCP surface on the site to 302 tools: the 197 available on any WordPress site plus these 105. This page documents the primary product, order, inventory, and report tools, then lists the v3.1, v3.2 and v4.0 groups; see the overview for the full list of areas.

Use this reference to understand capabilities and naming. For exact parameter and response shapes, inspect the tool calls in your AI assistant or logs.

Using the tool list in workflows

When you write prompts or design workflows, you can:

  • Refer to tools by name if you want to constrain behavior.
  • Describe outcomes in natural language and let the assistant choose tools.
  • Combine WooCommerce tools with existing WordPress tools for end-to-end flows.

For example:

  • "List the 50 best-selling products from last month and draft improved descriptions."
  • "Duplicate the current homepage hero product and set it as out of stock."
  • "Find all orders with failed payments this week and summarize issues."

The sections below group tools by area and summarize what each one does and how you might use it in workflows.


Product tools

Product tools manage WooCommerce products and their variations. Use them to browse, inspect, create, and update catalog items.

Product tools often work together. A common pattern is list → get → duplicate → update, which keeps edits safe and traceable.

woocommerce_list_products

List products that match basic filters such as status or search keywords.

filtersobject

Optional filter object such as status, category, or search text. Exact shape may vary between environments; check the tool output in your AI assistant.

paginationobject

Optional pagination controls such as page and per_page. Parameters vary; see the tool output in your AI assistant for the concrete structure.

Typical workflow uses:

  • Get an overview of the catalog before making changes.
  • Narrow down to a subset of products to pass into follow-up tools.
  • Build reports or summaries for specific product groups.

woocommerce_get_product

Retrieve full details for a single product by identifier.

product_idstring
Required

Unique product identifier as represented in your WooCommerce store. The assistant usually obtains this from woocommerce_list_products or another read tool.

Use this when:

  • You need the exact current state before editing.
  • You want to summarize or rewrite descriptions for a specific product.
  • You are about to duplicate or update a product and want to validate key fields.

woocommerce_create_product

Create a new product in WooCommerce.

product_dataobject
Required

High-level product definition such as name, price, status, and other attributes. The supported fields mirror WooCommerce product fields; see the tool output in your AI assistant for the exact schema.

Common workflows:

  • Generate new products from a CSV, spreadsheet, or external catalog.
  • Spin up draft products for campaign testing.
  • Create localized versions of an existing product for a new market.

woocommerce_update_product

Update an existing product.

product_idstring
Required

Identifier of the product to update, usually obtained from woocommerce_list_products or woocommerce_get_product.

updatesobject
Required

Partial update payload with only the fields you want to change. Exact field names map to WooCommerce product fields; confirm via the tool output in your AI assistant.

Use cases:

  • Adjust pricing or sale windows across selected products.
  • Update titles, descriptions, and SEO fields after AI rewrites.
  • Change product status (for example, draft, publish).

woocommerce_duplicate_product

Create a copy of an existing product, typically preserving key fields like pricing, attributes, and images.

product_idstring
Required

Identifier of the product to duplicate.

duplicate_optionsobject

Optional flags controlling what to copy or adjust in the duplicate, such as status or visibility. Options vary; inspect the tool output in your AI assistant for details.

Recommended patterns:

  • Duplicate first, then update the copy rather than editing live products.
  • Use duplicates as staging items for A/B tests.
  • Keep original products intact for rollback and comparison.

woocommerce_get_variations

List variations belonging to a variable product.

product_idstring
Required

Identifier of the parent variable product.

filtersobject

Optional filters such as status or specific attributes. Concrete fields depend on your WooCommerce configuration; see the tool output in your assistant.

Use this when:

  • You need to update stock or price at the variation level.
  • You want to analyze performance by size, color, or other attributes.
  • You are preparing targeted changes without affecting all variations.

Order tools

Order tools let your assistant inspect and manage WooCommerce orders. These tools are central for support workflows, fulfillment checks, and revenue reporting.

woocommerce_list_orders

List orders based on basic filters such as status, date range, or customer information.

filtersobject

Optional filter object, typically including status, created date range, or customer identifiers. Exact fields may differ; use tool output to see the structure.

paginationobject

Optional pagination controls to limit result size. Parameters vary by environment.

Common uses:

  • Retrieve all pending or processing orders for a period.
  • Build summary reports for revenue, refunds, or shipping delays.
  • Identify orders that may need manual review.

woocommerce_get_order

Fetch detailed information for a single order.

order_idstring
Required

Unique identifier of the order to retrieve. The assistant usually obtains this from woocommerce_list_orders or from user input.

Use this to:

  • Inspect line items, totals, and customer details.
  • Diagnose customer issues based on a specific order.
  • Prepare a safe update plan before changing order fields.

woocommerce_update_order_status

Change the status of an existing order.

order_idstring
Required

Identifier of the order to update.

statusstring
Required

New order status, aligned with your WooCommerce configuration (for example, pending, processing, completed, cancelled, refunded). Exact allowed values depend on your store.

Typical scenarios:

  • Mark orders as completed after external system checks.
  • Move orders to on-hold or cancelled based on fraud checks.
  • Coordinate status with a shipping or fulfillment integration.

woocommerce_update_order

Apply general updates to an order beyond status changes.

order_idstring
Required

Identifier of the order to update.

updatesobject
Required

Partial order update payload such as billing details, shipping details, or metadata. Field structure is store-specific; verify via the tool output in your AI assistant.

Use this power carefully:

  • Correct minor data issues like addresses or contact details.
  • Add metadata for internal workflows or external system references.
  • Coordinate refunds, adjustments, or manual notes.

Inventory tools

Inventory tools manage stock levels and stock status at the product or variation level.

Inventory changes can affect store availability and revenue. Combine these tools with confirmation prompts and audit logs to avoid unintended stock changes.

woocommerce_get_stock_status

Check stock status for one or more products or variations.

item_idsarray
Required

List of product or variation identifiers to check. The ID format follows your WooCommerce configuration.

Use this tool to:

  • Verify availability before running promotions.
  • Build low-stock and out-of-stock alerts.
  • Cross-check inventory between WooCommerce and external systems.

woocommerce_update_stock

Update stock levels or stock status.

updatesarray
Required

List of stock updates, each containing a target identifier and new stock data such as quantity or status. Exact fields depend on your store; inspect recent tool calls to see the concrete shape.

Recommended patterns:

  • Run read-only checks first with woocommerce_get_stock_status.
  • Use small, targeted batches and verify results.
  • Log context about why a stock change occurred for future audits.

Report tools

Report tools help your assistant generate summaries and analytics over order and product data.

woocommerce_sales_report

Generate a sales report over a time range.

rangeobject
Required

Time window for the report, typically including start and end dates. Precise field names vary; check the tool output in your AI assistant.

groupingstring

Optional grouping key such as day, week, month, product, or category. Supported values may differ between stores.

Common workflows:

  • Summarize revenue by period or product group.
  • Identify top-performing products or categories.
  • Feed results into AI-written summaries, presentations, or planning documents.

Safety and guardrails

WooCommerce tools can change live store data. Treat them with the same care you would give to direct database or dashboard changes.

Key practices:

  • Duplicate-first workflows: For product changes, prefer woocommerce_duplicate_product followed by woocommerce_update_product on the copy instead of editing live items.
  • Confirmation prompts: When you design prompts, ask the assistant to restate planned changes before applying them, especially for orders and inventory.
  • Read-only checks before writes: Call list or get tools first to verify you are targeting the correct items, then apply updates.

For detailed guidance on store safety, guardrails, and audit logging, see the WooCommerce safety notes.


Support and next steps

If you run into issues with WooCommerce tools or need help designing workflows, support is included. Contact the team at word@respira.press.

Complete tool list

The add-on registers 105 WooCommerce MCP tools (as of v4.0.0): the respira-woocommerce/ abilities plus the REST/MCP storefront-design, catalog, pricing, AI-readiness, feeds, cart-link, extension, configurator, reporting, store-configuration and webhook tools described in the overview and in the sections below. Every write is snapshot-backed, runs behind the manage_woocommerce capability, and supports dry_run where it changes data.

Products, categories, tags & brands

  • respira-woocommerce/get-products — List WooCommerce products
  • respira-woocommerce/get-product — Get a WooCommerce product by ID
  • respira-woocommerce/create-product — Create a WooCommerce product
  • respira-woocommerce/update-product — Update a WooCommerce product
  • respira-woocommerce/duplicate-product — Duplicate a WooCommerce product
  • respira-woocommerce/get-categories — List product categories
  • respira-woocommerce/get-category — Get a product category by ID
  • respira-woocommerce/create-category — Create a product category
  • respira-woocommerce/update-category — Update a product category
  • respira-woocommerce/delete-category — Delete a product category
  • respira-woocommerce/get-tags — List product tags
  • respira-woocommerce/get-tag — Get a product tag by ID
  • respira-woocommerce/create-tag — Create a product tag
  • respira-woocommerce/update-tag — Update a product tag
  • respira-woocommerce/delete-tag — Delete a product tag
  • respira-woocommerce/get-brands — List product brands
  • respira-woocommerce/get-brand — Get a product brand by ID
  • respira-woocommerce/create-brand — Create a product brand
  • respira-woocommerce/update-brand — Update a product brand
  • respira-woocommerce/delete-brand — Delete a product brand
  • respira-woocommerce/get-orders — List WooCommerce orders
  • respira-woocommerce/get-order — Get a WooCommerce order by ID
  • respira-woocommerce/update-order-status — Update order status
  • respira-woocommerce/get-stock-status — Inventory stock overview
  • respira-woocommerce/update-stock — Update product stock
  • respira-woocommerce/get-sales-report — Sales report

Variations, attributes & swatches

  • respira-woocommerce/get-variations — List product variations
  • respira-woocommerce/create-variation — Create a product variation
  • respira-woocommerce/update-variation — Update a product variation
  • respira-woocommerce/delete-variation — Delete a product variation
  • respira-woocommerce/generate-variations — Generate the variation matrix
  • respira-woocommerce/get-global-attributes — List global attributes
  • respira-woocommerce/create-global-attribute — Create a global attribute (incl. swatches)

Product configurator (Staggs)

  • respira-woocommerce/configurator-status — Configurator status
  • respira-woocommerce/list-configurator-attributes — List configurator attributes
  • respira-woocommerce/get-configurator-attribute-items — Get configurator attribute items
  • respira-woocommerce/set-configurator-attribute-items — Set configurator attribute items
  • respira-woocommerce/get-plugin-state — Get allow-listed plugin state
  • respira-woocommerce/set-plugin-state — Set allow-listed plugin state

Coupons

  • respira-woocommerce/get-coupons — List coupons
  • respira-woocommerce/get-coupon — Get a coupon
  • respira-woocommerce/create-coupon — Create a coupon
  • respira-woocommerce/update-coupon — Update a coupon
  • respira-woocommerce/delete-coupon — Delete a coupon

Customers

  • respira-woocommerce/get-customers — List customers
  • respira-woocommerce/get-customer — Get a customer
  • respira-woocommerce/create-customer — Create a customer
  • respira-woocommerce/update-customer — Update a customer
  • respira-woocommerce/delete-customer — Delete a customer

Orders, notes & refunds

  • respira-woocommerce/get-order-notes — List order notes
  • respira-woocommerce/add-order-note — Add an order note
  • respira-woocommerce/get-order-refunds — List order refunds
  • respira-woocommerce/create-order-refund — Refund an order

Agent-ready commerce and extension tools (v3.1 and v3.2)

The v3.1 and v3.2 releases added six groups. MCP tool names below; each also registers as a WordPress Ability for browser AI.

Product feeds and llms.txt

  • woocommerce_configure_feed — enable formats, schedule, options; returns the public feed URLs
  • woocommerce_generate_feed — kick a rebuild (idempotent; first batch runs synchronously so it works even when wp-cron is dead)
  • woocommerce_get_feed_status — manifest, per-format freshness, wp-cron health warning
  • woocommerce_validate_feed — check rows against each platform's actual spec before registering
  • woocommerce_set_feed_category_mapping — map your categories to the Google product taxonomy

Readiness score and autofix

  • woocommerce_product_ai_readiness / woocommerce_catalog_ai_readiness — the 0-100 score, per product and store-wide
  • woocommerce_readiness_fixlist — the scan as an ordered work queue, weakest products first, each failing check paired with the tool that fixes it
  • woocommerce_set_image_alt — write image alt text (the check that fails most often); GTIN and gallery writes live on woocommerce_update_product
  • woocommerce_create_cart_link — a signed URL that fills the cart server-side and lands on your own checkout; tampered signatures get a 403
  • woocommerce_agent_orders_report — orders and revenue attributed to AI-assistant sources

Subscriptions (WooCommerce Subscriptions)

  • woocommerce_list_subscriptions, woocommerce_get_subscription, woocommerce_update_subscription_status (every transition validated against what Subscriptions itself allows), woocommerce_update_subscription_dates, woocommerce_add_subscription_note

Bookings and Memberships (WooCommerce Bookings, Memberships)

  • woocommerce_list_bookings, woocommerce_get_booking, woocommerce_update_booking_status, woocommerce_reschedule_booking (conflict scan before anything moves)
  • woocommerce_list_membership_plans, woocommerce_list_memberships, woocommerce_get_membership, woocommerce_update_membership_status, woocommerce_set_membership_end_date

All extension writes are dry-run by default and require the real extension plugin to be active.

Product configurator (STAGGS, v3.2)

  • woocommerce_configurator_status, woocommerce_get_product_configurator, woocommerce_set_product_configurator — detect STAGGS, read and enable/disable the configurator per product
  • woocommerce_list_configurator_attributes, woocommerce_get_configurator_attribute_items, woocommerce_set_configurator_attribute_items — read attribute groups and rewrite option items (labels, prices, defaults) through the STAGGS/Carbon Fields helpers
  • woocommerce_get_plugin_state, woocommerce_set_plugin_state — allow-listed plugin settings; any key outside the known-safe set refuses the whole request

Storefront, reporting, configuration and webhooks (v4.0)

v4.0.0 requires Respira for WordPress plugin 8.0.0 or newer.

Storefront intelligence, FSE-first

Storefront analysis no longer assumes a page builder. On a block theme it runs against the native archive-product template and returns real structural analysis instead of "no page builder detected". Where a page builder is present, the existing builder path still runs.

Two behaviours worth knowing before you call a storefront write:

  • Badges land inside the product image. Sale and low-stock badges are positioned inside the product image, matching WooCommerce's own product card. If a badge is already there, the write is refused as a no-op rather than duplicated, so re-running a prompt does not stack badges.
  • Product-card fields are addressed by canonical block name. Use the WooCommerce block name: woocommerce/product-image, woocommerce/product-price, woocommerce/product-title, woocommerce/product-button. Requested attributes are intersected with the installed block's registered attributes, so an unrecognised attribute key is refused rather than silently accepted and dropped.

Reporting

Bounded, HPOS-compatible reporting. Every report has a hard bound so a broad question cannot walk the whole order table.

  • Revenue reporting over a date range
  • Sales time-series
  • Top-product reporting
  • Order reporting
  • Customer reporting, privacy-safe by default

Store configuration discovery (read-only)

Read what the store is actually configured to do before changing anything around it. These are reads. They do not write.

  • Store configuration
  • Payment gateways
  • Shipping zones
  • Tax rates

Native WooCommerce webhooks (approval-gated)

Webhook management is the one v4.0 write path that leaves your site, so it is fenced:

  • Approval-gated. A webhook change is staged for a human to approve.
  • HTTPS targets only. A plain HTTP delivery URL is refused.
  • Allowlisted topics only. A topic outside the allowlist is refused.
  • Write-only secrets. A secret can be set, never read back.