Skip to main content
Glama

woo_helper_list_invoice_orders

List WooCommerce invoice orders filtered by status—done, dry_run, queued, retry, or failed—for a specified site to track invoice processing and troubleshoot failures.

Instructions

Orders by invoice status: done, dry_run, queued, retry or failed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "woo_helper_list_invoice_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about read-only vs mutating behavior, pagination, result size, or what an 'invoice order' record contains. Only the status vocabulary is disclosed, which is already in the schema.

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

Conciseness3/5

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

It is a single short sentence with no filler, but it is a sentence fragment that is arguably under-specified rather than concise. The status list is front-loaded, which is fine, but the whole definition is thinner than the tool's complexity warrants.

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

Completeness2/5

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

With no annotations, no output schema, and a two-parameter schema, the description should explain what is returned, how results are scoped per site, and how status filtering behaves. None of that is present, leaving significant gaps for an agent to call this correctly.

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

Parameters2/5

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

Schema coverage is 50%: 'site' has a description pointing to list_sites, while 'status' has only an enum. The description merely restates the enum values without explaining what each status means (e.g., dry_run vs queued vs retry) or whether status is optional and what omitting it returns.

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

Purpose3/5

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

The description names the resource (invoice orders) and the filter dimension (invoice status), but the verb 'Orders by' is ambiguous — it does not clearly say this retrieves/lists records rather than sorting them. It also does not distinguish itself from nearby siblings such as woo_list_orders or woo_helper_get_invoice_order.

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 guidance on when to use this tool versus woo_list_orders, woo_helper_get_invoice_order, or woo_helper_get_invoices, and no stated preconditions or exclusions. The agent must infer the use case entirely from the name and the status enum.

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

Deploy Server

Other Tools