Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

trustpilot_business_search

Search Trustpilot business units by query and country to retrieve TrustScore, ratings, review counts, categories, contact details, and profile URLs.

Instructions

Search Trustpilot business units. Searches Trustpilot for businesses matching a query, for a country (default US), with page and page_size (default 20, max 100). Each result has the display name, identifying name, TrustScore, star rating, review count, categories, website, email, phone, address and Trustpilot URL; total_hits gives the full match count.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
pageNo1-based page number; defaults to 1
countryNoTwo-letter country code; defaults to US
page_sizeNoResults per page; defaults to 20, maximum 100

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?

With no annotations provided, the description carries the disclosure burden and does reasonably well: it defines defaults (country US, page_size 20) and a hard ceiling (max 100), and enumerates exactly what each result contains plus the total_hits count. It omits any auth/rate-limit or error behavior, keeping it short of 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.

Conciseness4/5

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

Front-loaded with the core operation, then a single dense sentence covering params and result shape. The second clause ('Searches Trustpilot for businesses matching a query') slightly restates the opening sentence, a minor redundancy, but nothing else is wasted.

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 read-only search tool with no annotations and no output schema, the description compensates well by spelling out the returned fields and total_hits so the agent knows what comes back. It could still say more about matching behavior or failure modes, but the essentials for correct invocation are present.

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 all four parameters are already documented (q, page, country, page_size with defaults and max). The description largely restates those same specifics, adding no new syntax, format, or matching-behavior detail beyond the schema, so the 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+resource ('Search Trustpilot business units') and immediately clarifies it searches for businesses matching a query, so the operation is unambiguous. However, it never distinguishes itself from neighboring tools like trustpilot_business (single-business lookup) or trustpilot_category_search, so an agent must infer the split.

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: 'for businesses matching a query' suggests keyword discovery, and the country/page params imply broad result browsing. There is no explicit when-to-use or when-to-prefer-an-alternative statement (e.g., versus trustpilot_business for a known domain or trustpilot_category_search for category browsing).

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