Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

trustpilot_business_reviews

Fetch Trustpilot business reviews by slug, filter by stars, verified status, replies, language, or text search, and get ratings, author details, dates, replies, and pagination.

Instructions

Get Trustpilot business reviews. Returns one page of Trustpilot reviews for a business slug such as openai.com, with filters for star rating, verified reviews, reviews with a company reply, language and text search. Each review has its rating, title, body, author name, country and review count, dates, and any company reply; the response also carries the business summary and pagination totals.

Input Schema

NameRequiredDescriptionDefault
qNoText search within reviews
pageNo1-based page number; defaults to 1
slugYesTrustpilot business slug
starsNoFilter by star rating from 1 to 5
date_toNoDate range end in YYYY-MM-DD; currently rejected by upstream
repliedNoFilter to reviews with business replies
languageNoReview language code used by Trustpilot
verifiedNoFilter to verified reviews
date_fromNoDate range start in YYYY-MM-DD; currently rejected by upstream

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations, so the description carries the full burden, and it does disclose the return shape well: one page of reviews, per-review fields (rating, title, body, author, country, dates, company reply), plus business summary and pagination totals. It omits auth/rate-limit behavior, but for a read-only listing tool the pagination and output disclosure is substantive.

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

Conciseness4/5

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

Two sentences, front-loaded with the purpose and scope before the response detail. The second sentence is dense with output fields but every listed field earns its place by telling the agent what a review contains.

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?

With no output schema, the description correctly compensates by describing the returned review fields, business summary, and pagination totals. It does not mention that date_from/date_to are rejected upstream (only the schema does), leaving a small gap for a 9-param tool.

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; the description's filter enumeration (star rating, verified, replied, language, text search) largely restates the schema. It adds context that these are the filters but no syntax or format detail beyond what the schema provides, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('Get Trustpilot business reviews') and scopes it precisely: one page of reviews for a business slug like `openai.com`. It is clearly a review-listing tool, distinguishable from the sibling trustpilot_business detail tool by the resource, though it never names that sibling explicitly.

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 rather than stated: the agent learns it needs a business slug and that star/verified/replied/language/text filters exist. There is no explicit when-to-use vs when-not, and no routing to trustpilot_business or trustpilot_business_search as alternatives.

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