Skip to main content
Glama

WooCommerce: List products

woocommerce_list_products
Read-only

Retrieve WooCommerce product listings with key details like price, stock, category, and image for catalog discovery or content planning. Filter by status, price, stock, search terms, and date ranges.

Instructions

[UNIFIED] List WooCommerce products for catalog discovery and editorial/content workflows. Returns lightweight pricing, stock, category/tag, image, permalink, and modified-date fields without full descriptions by default.

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": "woocommerce_list_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
pageNo
siteYes
afterNo
orderNo
beforeNo
searchNo
statusNoany
on_saleNo
orderbyNo
categoryNo
featuredNo
per_pageNo
max_priceNo
min_priceNo
search_termsNo
stock_statusNo
modified_afterNo
include_contentNo
modified_beforeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description only needs to add context. It does add useful value by describing the lightweight payload (pricing, stock, category/tag, image, permalink, modified-date) and the default omission of full descriptions, but says nothing about pagination limits, result caps, or error behavior.

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 tight sentences with no filler, and the payload expectation is front-loaded after the purpose. The "[UNIFIED]" prefix is a minor piece of noise but the rest earns its place.

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 20-parameter list tool with zero schema descriptions and no output schema, the definition is under-specified. It compensates partially by describing the return shape, which is needed given no output schema, but it leaves an agent guessing at filter formats, pagination behavior, and how the many optional filters combine.

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 description coverage is 0% across 20 parameters, so the description carries the full burden and largely fails. Only include_content is indirectly explained ("without full descriptions by default"); the filters for tag, category, search, price range, stock_status, dates, orderby, on_sale and featured get no meaning or format guidance at all.

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 clear verb plus resource ("List WooCommerce products") and names the intended job (catalog discovery, editorial/content workflows). It is distinguishable from woocommerce_get_product by the plural list framing, though no sibling 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 Guidelines3/5

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

The phrase "for catalog discovery and editorial/content workflows" implies when to reach for this tool, but there is no explicit when-not guidance and no routing to woocommerce_get_product for full descriptions or to the variation/category list siblings.

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