Skip to main content
Glama
Jacques-Murray

WooCommerce MCP Server

List WooCommerce Orders

woocommerce_list_orders
Read-onlyIdempotent

Retrieve a filtered list of WooCommerce orders by status, customer, date range, or product. Supports pagination and sorting for efficient order management.

Instructions

Search and list store orders, with filters for status, customer, date range, and product.

Args:

  • status: 'any'|'pending'|'processing'|'on-hold'|'completed'|'cancelled'|'refunded'|'failed'|'trash' (default: any)

  • customer (number, optional): customer ID

  • search (string, optional)

  • after / before (string, optional): ISO8601 dates bounding date_created

  • product (number, optional): only orders containing this product ID

  • orderby / order: sorting (default date/desc)

  • page / per_page: pagination (default page=1, per_page=20, max 100)

  • response_format ('markdown'|'json'): default 'markdown'

Returns: paginated list of orders with id, number, status, total, currency, customer, and line item count.

Examples:

  • Use when: "show me pending orders from this week" -> status="pending", after="2026-06-29T00:00:00"

  • Use when: "how many orders has customer 15 placed" -> customer=15

  • Don't use when: you need full line-item and address detail for one order (use woocommerce_get_order)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number to retrieve, 1-based (default: 1)
afterNoISO8601 date - only orders created after this date
orderNoSort direction (default: desc)desc
beforeNoISO8601 date - only orders created before this date
searchNoSearch term (matches order number, billing details, etc.)
statusNoFilter by order status (default: any)any
orderbyNoSort field (default: date)date
productNoFilter to orders that contain this product ID
customerNoFilter to orders from a specific customer ID
per_pageNoNumber of results per page, 1-100 (default: 20)
response_formatNoOutput format: 'markdown' for human-readable text or 'json' for machine-readable structured datamarkdown
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context beyond annotations: pagination details (default per_page=20, max 100), response format options, and what fields are returned. It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with an introductory sentence, parameter list, return info, and examples. It is not excessively verbose, though it could be slightly tighter. Still, every sentence adds value and is front-loaded with the main purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 11 parameters, no required, and no output schema, the description covers all parameters, explains return fields (id, number, status, total, currency, customer, line item count), and notes pagination limits. This is sufficient for an agent to understand the tool's behavior and output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds extra value by listing all parameters with defaults, providing usage examples (e.g., status, after, customer), and clarifying the search parameter matches billing details. This goes beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool 'Search and list store orders' with specific filters. It distinguishes from the sibling tool 'woocommerce_get_order' by noting when not to use it for full detail, and from other list tools by focusing on orders.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit use cases with examples ('show me pending orders from this week') and explicitly tells when not to use this tool ('Don't use when: you need full line-item and address detail for one order (use woocommerce_get_order)'). This gives clear guidance on when to use vs alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jacques-Murray/woocommerce-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server