Skip to main content
Glama

wc_list_products

Lists WooCommerce products with filters for search text, SKU, stock status, and status; supports pagination to browse results.

Instructions

List WooCommerce products. Filter by search text, SKU or stock 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_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuNo
pageNoPage number
searchNo
statusNoany
per_pageNoResults per page (max 50)
stock_statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 behavioral burden and does not meet it. It never states that this is a read-only paginated listing, that results default to 10 per page with a 50 cap, that status defaults to "any" (so drafts and private products are returned alongside published ones), or anything about ordering or the response shape.

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?

Two short sentences with the resource and the filter axes front-loaded and no filler. It is efficient, though the terseness leaves little room for the behavioral detail the tool needs.

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?

For a six-parameter listing tool with no annotations, no output schema, and low schema coverage, the description is under-specified. Missing pagination defaults, the meaning of the default status="any", and any return-shape hint leaves real gaps an agent would hit on first invocation.

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 description coverage is only 33%, so the description should compensate, and it partially does by surfacing search, SKU, and stock status as the filterable dimensions. However, it omits the status, page, and per_page parameters entirely, and adds no meaning beyond the schema names for the three it does mention (e.g. SKU match semantics, partial vs exact search).

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?

The description states a specific verb and resource ("List WooCommerce products"), which clearly separates it from write-side siblings like wc_create_product and single-item siblings like wc_get_product. It does not explicitly name any sibling as an alternative, so it stops short of the top band.

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?

The second sentence names three filter dimensions, which is a weak implicit usage hint, but there is no statement of when to prefer this over wc_get_product or a report tool, and no exclusions or prerequisites. An agent gets no routing guidance beyond the obvious verb.

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