Fetch Trustpilot category details by slug, including metadata, company cards, and side rails from public category pages.
Get Trustpilot category detail. Returns category metadata, company cards, and side rails from Trustpilot's public category page.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page number; defaults to 1 | |
| slug | Yes | Trustpilot category slug |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey the tool's behavioral traits. It mentions the return structure but does not disclose whether the operation is read-only, requires authentication, has rate limits, or any other side effects. For a tool with no annotations, this is a significant gap in transparency.
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 concise: two sentences, with the first stating the core purpose and the second listing the return data. Every word adds value, and it is front-loaded with the action. No wasted words.
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 no output schema, the description adequately explains what the tool returns: category metadata, company cards, and side rails. It also hints at pagination via the page parameter, though it does not explicitly state that company cards may span multiple pages. For a simple tool with two parameters, this is largely complete, but a brief mention of pagination or authentication would improve it.
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?
Both parameters have descriptions in the schema (slug and page). The description adds no additional meaning beyond what the schema already provides. Since schema coverage is 100%, the baseline of 3 is appropriate, and no bonus points are earned.
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 clearly states 'Get Trustpilot category detail' with a specific verb and resource, and lists the returned components (category metadata, company cards, side rails). It distinguishes itself from siblings like trustpilot_categories (which lists categories) and trustpilot_category_search (which searches categories) by focusing on a single category's detailed page.
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?
There is no guidance on when to use this tool versus its siblings. With multiple trustpilot category-related tools available, the description fails to specify that this is for retrieving detailed information about a specific category, while trustpilot_categories or trustpilot_category_search might be more appropriate for browsing or searching.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.