Inicio - Documentación - POM AI - 17 MCP - WooCommerce product tools - `wc_get_store_stats`: read store statistics

wc_get_store_stats: read store statistics

Aggregate counts for the catalogue. Deliberately narrow: catalogue only, no sales data.

Arguments

None.

Permissions

mcp:read and woocommerce:catalog:read, plus manage_woocommerce or edit_products.

What it returns

Field Meaning
products Product counts by post status
coupons Coupon counts by post status
attributes How many global attributes exist

The product and coupon figures are broken down by status — published, draft, private, trash and any other registered status.

No sales data, deliberately

The tool's own description says catalog stats only, and that is the boundary: no orders, no revenue, no customers, no refunds, no stock valuation.

Those live in a different part of WooCommerce and are not exposed by any MCP tool. An assistant asked "how are sales this month?" cannot answer, and should not appear to. See What POM AI MCP does not expose.

It is the missing total for product listings

wc_get_products returns no total and caps at 100 per page. This tool is how you find out whether a listing was complete.

Get the store stats, then list the first 100 products, and tell me whether that is all of them.

Without it, an assistant that lists once will reason about a hundred products as if they were the catalogue — and a bulk price rule based on that assumption silently skips the rest.

The status breakdown is the useful part

  • A large draft count means unfinished products a broad instruction might touch.
  • A large trash count means deletions not yet purged, and products still occupying SKUs.
  • publish well below the total means most of the catalogue is not live.

Before agreeing to anything catalogue-wide, know these numbers.

The attributes count sets expectations

A shop with many global attributes is one where variable products are the norm, and price work will mostly happen on variations rather than products.

A count of zero means no global attributes exist, so any variable product uses per-product custom attributes instead. See wc_get_product_attributes.

Coupon counts belong here too

Coupons are counted by this tool even though their own tools live in Coupon tools. A large trash count is worth noticing before anyone uses wc_empty_coupon_trash.

Using it well

At the start of any shop session:

Get the store stats and show me the product and coupon breakdowns.

That one call tells you the shape of the shop, whether listings will be complete, and whether there is a backlog of drafts or trash — before you agree to change anything.

Common problems

Symptom Cause
The tool is missing WooCommerce is not active
pom_ai_mcp_wc_forbidden Missing shop capability
Counts higher than the shop appears to have Trash and drafts are included
No sales figures Correct; catalogue only
attributes is 0 No global attributes are defined

Related