Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

trustpilot_business_search

Search Trustpilot for business profiles using query, country, and pagination. Returns normalized results from Trustpilot's API.

Instructions

Search Trustpilot business units. Returns normalized business-unit search results from Trustpilot's JSON business-unit search API.

Input Schema

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

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

No annotations provided, so description must disclose behavioral traits. Only mentions 'normalized' results, but omits auth requirements, rate limits, or any side effects. Minimal behavioral insight.

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?

Single sentence plus an explanation of return source. No fluff, but could benefit from slightly more structure (e.g., bullet points). Highly efficient.

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 search tool with 4 params fully described in schema and no output schema, description states source and normalization. Could hint at response structure, but overall adequate.

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 covers all 4 parameters with descriptions, so the tool description adds no extra value beyond what's in the schema. Baseline 3 is appropriate.

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?

Clearly states it searches Trustpilot business units and returns normalized results. Differentiates from sibling tools like trustpilot_business (single unit lookup) and trustpilot_category_search.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., trustpilot_business for specific ID lookup, trustpilot_business_reviews for reviews). Lacks any when/when-not instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server