woo_top_sellers
Find your WooCommerce store's top-selling products by defining the sales period and result count.
Instructions
Get top selling products
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| period | No | month | |
| limit | No |
Find your WooCommerce store's top-selling products by defining the sales period and result count.
Get top selling products
| Name | Required | Description | Default |
|---|---|---|---|
| period | No | month | |
| limit | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must disclose behavioral traits. It fails to mention that this is a read-only operation, any authentication requirements, or what impacts the tool has on data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely brief but under-specified. It does not earn its place as it omits essential details about parameters and behavior, making it insufficient for guiding an AI agent.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (2 optional parameters, no output schema), the description is severely incomplete. It does not explain the meaning of 'top selling', the role of the period parameter, or the structure of the output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, yet the description provides no information about the 'period' and 'limit' parameters. This leaves the agent without context for parameter usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Get top selling products' clearly states the verb and resource, making the purpose evident. However, it does not differentiate from sibling tools like woo_sales_report, which could cause confusion.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives or context for usage. The description lacks any when-to-use or when-not-to-use information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cvrt-jh/wordpress-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server