Skip to main content
Glama

woocommerce_get_top_sellers

Retrieve top-selling products from WooCommerce stores by sales quantity for specified time periods to identify best-performing items.

Instructions

[UNIFIED] Get top selling products report. Returns products with highest sales quantities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYes
periodNoweek
date_minNo
date_maxNo
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool returns products, but fails to mention whether the operation is read-only, if there are rate limits, pagination behavior, or the response format. The '[UNIFIED]' prefix is unexplained metadata.

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?

The description is brief (two sentences), but the '[UNIFIED]' tag at the beginning is unexplained noise. Given the complete lack of parameter documentation in the schema, the description is actually insufficiently detailed rather than efficiently concise.

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 reporting tool with 4 parameters and no output schema, the description is inadequate. It omits critical details like date format expectations for the range filters, valid period values, and what data fields are included in the returned top-sellers report.

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

Parameters1/5

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

Schema description coverage is 0% and the description completely fails to compensate. It provides no information about the 'site' parameter (format/identifier), valid values for 'period' (beyond the default 'week'), or expected date formats for 'date_min' and 'date_max'. The parameters are entirely undocumented.

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 clearly states it retrieves a 'top selling products report' and clarifies that 'top sellers' means 'products with highest sales quantities.' However, it does not explicitly differentiate from the sibling tool `woocommerce_get_sales_report`, which could cause confusion between general sales data and top-seller rankings.

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 description provides no guidance on when to use this tool versus alternatives like `woocommerce_get_sales_report` or `woocommerce_list_products`. There are no prerequisites, filtering recommendations, or exclusion criteria mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/airano-ir/mcphub'

If you have feedback or need assistance with the MCP directory API, please join our Discord server