Skip to main content
Glama
Sign In
mcp-server-woocommerce

mcp-server-woocommerce

by AmitGurbani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_product_totals

Read-only

Count products by status (publish, draft, pending, private) to get a quick catalog size overview.

Instructions

Get product counts grouped by status (publish, draft, pending, private). Quick catalog size overview.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated fields to return (default: slug,name,total)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, covering safety. The description adds the grouping behavior by status and the quick-overview intent, but does not disclose other behavioral traits like pagination, limits, or response format. With the lower bar due to annotations, this is adequate but not rich.

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?

The description is two short sentences, front-loading the core action and status groupings, with no wasted words. The second sentence efficiently adds the use-case context.

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

Completeness5/5

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

For a simple tool with one optional parameter, no output schema, and strong annotations, the description is sufficient. It conveys the essential purpose, grouping dimensions, and the quick-overview use case. The parameter details are covered by the schema.

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 100% for the single optional 'fields' parameter, with a description providing default and format. The tool description itself adds no extra parameter context, so the schema does the heavy lifting. Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states a specific verb and resource: 'Get product counts grouped by status', and enumerates the statuses (publish, draft, pending, private). This distinguishes it from sibling tools like get_product and list_products, and aligns with the pattern of other totals tools (get_order_totals, get_customer_totals).

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?

Usage context is implied via 'Quick catalog size overview', suggesting it's for summaries rather than detailed product listings, but there is no explicit when-to-use or alternative guidance. No exclusions or alternatives are named, so it doesn't reach the level of explicit guidelines.

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