List WooCommerce orders by site, status, date range, product, customer, or page to review and manage store sales.
List WooCommerce orders
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| site | Yes | Site id (see list_sites) | |
| after | No | Orders after date (YYYY-MM-DD) | |
| before | No | Orders before date (YYYY-MM-DD) | |
| status | No | any | |
| product | No | Product ID | |
| customer | No | Customer ID | |
| per_page | No |
Changes observed during successful MCP inspections.
v3.4.0Input schema / properties / siteAdded value: +{
+ "description": "Site id (see list_sites)",
+ "type": "string"
+}Input schema / requiredAdded value: +[
+ "site"
+]v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not disclose read-only behavior, pagination behavior, default result limits, permissions, or return format, despite the schema exposing page, per_page, and filter parameters.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded phrase with no wasted words. It is concise, but it is too thin for a tool with eight parameters, so it lands at minimum viable rather than fully appropriate.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the 8-parameter schema, no annotations, no output schema, and 63% parameter description coverage, the description is incomplete. It omits filtering behavior, pagination defaults, and what the returned order list contains.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds no parameter meaning beyond the schema. With 8 parameters and only 63% schema description coverage, the undocumented parameters such as page, status, and per_page are not clarified anywhere.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'List WooCommerce orders.' That is clear enough for an agent to know the tool returns a collection of orders. However, it does not differentiate this tool from siblings such as woo_get_order, woo_get_customer_orders, or woo_sales_report.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no usage context, exclusions, or alternatives. It does not explain when to use this list tool versus retrieving a single order or pulling customer-specific orders.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.