Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

trustpilot_business_related

Find related Trustpilot businesses for a business slug and return names, star ratings, TrustScores, review counts, and URLs.

Instructions

Get Trustpilot related businesses. Returns the businesses Trustpilot shows as related to a given business slug such as openai.com. Each related business has its display name, identifying name, logo, star rating, TrustScore, review count and Trustpilot URL; the response also includes a summary of the business you asked about.

Input Schema

NameRequiredDescriptionDefault
slugYesTrustpilot business slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does signal read-only behavior through 'Get' and 'Returns'. It also discloses the returned business fields and that a summary of the queried business is included, though it omits edge cases like empty results or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded, well structured, and free of repetition. The field list earns its place because it compensates for the lack of an output schema without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool with no output schema, the description does the important work of explaining the returned businesses and the included summary. It could be slightly more complete by clarifying what the summary contains or how empty related lists are represented.

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

Parameters4/5

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

Schema description coverage is 100%, so the slug parameter is already documented in the schema. The description adds a useful concrete example (`openai.com`) that clarifies the expected slug format beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: getting businesses Trustpilot shows as related to a given business slug. It clearly distinguishes this from sibling tools like trustpilot_business, trustpilot_business_reviews, and trustpilot_business_search by focusing on related-business discovery.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the familiar pattern of using a business slug to retrieve related businesses. However, there is no explicit guidance on when to choose this tool instead of trustpilot_business, trustpilot_business_search, or trustpilot_business_reviews.

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

Deploy Server

Other Tools