Crawlora MCP

trustpilot_business

Read-only

Fetch a Trustpilot business profile by its slug, including display name, profile URL, TrustScore, and review count. Use trustpilot_business_search to find a slug, trustpilot_business_reviews to read reviews, or trustpilot_business_related to discover similar businesses.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "trustpilot_business"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Resource slug.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the set of fields a profile contains, but that overlaps with the output schema, and it discloses nothing about auth requirements, rate limits, or freshness. With annotations carrying the safety burden, a 3 is appropriate.

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?

Two sentences with zero waste: the purpose leads and the sibling routing follows. Front-loaded and tightly scoped.

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

Completeness5/5

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

For a single-parameter read-only fetch with an output schema and full annotation coverage, the description is complete. Return values need not be explained since an output schema exists, and none of the routing information an agent needs is missing.

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 coverage is 100%, so the schema documents the slug parameter, giving a baseline of 3. The description goes slightly further by naming the slug as a lookup key and pointing to trustpilot_business_search as the way to obtain it, adding real value about where the value comes from.

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?

States a specific verb (Fetch) and resource (Trustpilot business profile) and enumerates the key fields returned (display name, profile URL, TrustScore, review count). This clearly distinguishes it from trustpilot_business_search, trustpilot_business_reviews, and trustpilot_business_related without needing to open any schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use trustpilot_business_search to find a slug, trustpilot_business_reviews to read reviews, and trustpilot_business_related to discover similar businesses. Each alternative is named with the condition that selects it, leaving nothing to inference.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?