Fetch a Trustpilot business profile summary parsed from its public page to review ratings, reviews, and company details using a business slug.
Get Trustpilot business profile. Returns a summary Trustpilot business profile parsed from the public business page.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Trustpilot business 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 present, so the description must fully disclose behavior. It only states the return type (summary profile) and source (public business page). It does not mention input requirements (e.g., valid slug), error handling, or that the operation is read-only. For a simple read tool, more transparency is expected.
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 a single, efficient sentence that front-loads the verb and resource. Every word contributes meaning, with no redundancy or filler.
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 low complexity (one required parameter, no output schema, no nested objects), the description provides the core purpose and return type. However, it lacks details on behavioral expectations (e.g., idempotency, data freshness) that would make it complete for reliable agent use.
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?
The input schema defines one parameter 'slug' with the description 'Trustpilot business slug'. The tool description does not add further semantic meaning beyond the schema. With 100% schema coverage, a baseline score of 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 clearly states the verb 'Get' and the resource 'Trustpilot business profile', and mentions it parses from the public business page. It distinguishes itself from sibling tools like 'trustpilot_business_reviews' by focusing on the profile summary, but does not explicitly contrast with alternatives.
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 explicit guidance is provided on when to use this tool versus siblings like trustpilot_business_search or trustpilot_business_reviews. The usage is implied by the function description, but no when-not-to-use or alternative cues are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.