Skip to main content
Glama

wc_list_orders

Lists WooCommerce orders newest first and filters by status, with pagination for reviewing recent or specific order states.

Instructions

List WooCommerce orders, newest first. Filter by status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wc_list_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
statusNoany
per_pageNoResults per page (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does contribute one useful behavioral fact (newest-first ordering), but says nothing about result size, pagination limits, empty results, required permissions, or what an order record contains.

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

Conciseness5/5

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

Two short sentences with zero waste, and the ordering behavior is front-loaded where an agent will see it. Nothing needs trimming and nothing is padded.

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

Completeness3/5

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

For a simple three-parameter list tool with no output schema, the description covers the essentials of what it returns but omits pagination expectations and result shape. It is minimally sufficient rather than complete.

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

Parameters3/5

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

Schema coverage is 67%, and 'filter by status' adds meaning for the one parameter the schema leaves undocumented (the status enum has no description text). Page and per_page are already explained by their schema descriptions, so nothing further is added for them, and the 'any' default semantics are not clarified.

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

Purpose4/5

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

States a specific verb and resource ('List WooCommerce orders') plus the default ordering ('newest first'), so an agent knows exactly what it retrieves. The resource name itself distinguishes it from the product/post siblings, but no sibling or alternative is named explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says to prefer this over wc_sales_report for aggregate data or wc_get_order for a single order. The only implied usage is filtering by status, with no conditions or exclusions stated.

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