Browse Whatnot live shows by category to return current and upcoming listings, including seller, title, status, start time, thumbnail, and tags.
Browse Whatnot live shows by category. Returns the live and upcoming shows currently listed under a Whatnot category: seller, title, status, start time, thumbnail, and tags.
| Name | Required | Description | Default |
|---|---|---|---|
| category | Yes | Whatnot category slug. See GET /whatnot/categories for the full list. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It helpfully states that results include live and upcoming shows with seller, title, status, start time, thumbnail, and tags, but it does not mention pagination, limits, authentication, or other operational behavior.
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 two tight sentences with no filler. The core action and scope are front-loaded, followed by useful return-field detail.
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?
For a simple one-parameter browse tool with a fully documented schema, the description is largely complete. It covers the returned data despite having no output schema, though pagination and result limits are not addressed.
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 100%, and the single category parameter is fully documented in the schema, including a pointer to the categories endpoint. The description only repeats the category scoping at a high level, so baseline 3 is appropriate.
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 gives a clear verb and resource: browse Whatnot live shows by category. It also states the returned fields and clarifies that it covers live and upcoming shows. It does not explicitly distinguish itself from nearby siblings such as whatnot_categories or whatnot_live, so it falls short of a 5.
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?
Usage is implied by 'Browse ... by category,' but there is no explicit when-to-use guidance, no exclusions, and no named alternatives. An agent can infer the use case, but the description does not route it against sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.