Crawlora MCP

trustpilot_business_reviews

Read-only

Fetch one page of public Trustpilot review items for a known business slug, with optional rating and language filters. Use trustpilot_business_search to find a business and its slug first.

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>",
      "Page": "<Page>",
      "Stars": "<Stars>",
      "Verified": "<Verified>",
      "Replied": "<Replied>",
      "Language": "<Language>",
      "Query": "<Query>",
      "DateFrom": "<DateFrom>",
      "DateTo": "<DateTo>"
    },
    "name": "trustpilot_business_reviews"
  }
}

Input Schema

Name	Required	Description
`Page`	Yes	1-based result page, default 1, minimum 1.
`Slug`	Yes	Trustpilot business slug, e.g. openai.com.
`Query`	Yes	Text search within review content, e.g. refund.
`Stars`	Yes	Filter by star rating, 1 to 5.
`DateTo`	Yes	Date range end in YYYY-MM-DD; currently rejected by upstream.
`Replied`	Yes	Filter to reviews that have a business reply when true.
`DateFrom`	Yes	Date range start in YYYY-MM-DD; currently rejected by upstream.
`Language`	Yes	Review language code used by Trustpilot, e.g. en.
`Verified`	Yes	Filter to verified reviews only when true.

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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: results are limited to one page at a time and only public review items are returned. It omits rate-limit and pagination-termination behavior, which keeps it from a 5.

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, zero padding, with the tool's scope front-loaded and the prerequisite second. Every clause earns its place.

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?

An output schema exists, so return values need not be described. Purpose, scope, prerequisite discovery, and filter availability are all covered; nothing essential for a correct call is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all nine parameters, and the baseline is 3. The description only alludes to 'rating and language filters' and even labels them optional while the schema marks every parameter required (with DateFrom/DateTo currently rejected upstream), so it adds no real clarity over the schema and is mildly at odds with it.

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 and resource ('Fetch one page of public Trustpilot review items') with the key scope constraint (single page, known business slug). It also names the sibling tool trustpilot_business_search, so an agent can distinguish this review-fetching tool from the business lookup siblings without opening either schema.

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

Usage Guidelines4/5

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

Gives an explicit prerequisite ('Use trustpilot_business_search to find a business and its slug first'), which is exactly the routing information an agent needs. It does not state when NOT to use this tool (e.g. vs. trustpilot_business_reviews-like alternatives or category-level review browsing), so it stops just short of a 5.

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?