Crawlora MCP

trustpilot_business_search

Read-only

Search Trustpilot business profiles by query and optional country, returning paginated results. Use trustpilot_business for one slug or trustpilot_category_search to browse a business category.

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": {
      "Query": "<Query>"
    },
    "name": "trustpilot_business_search"
  }
}

Input Schema

Name	Required	Description
`Page`	No	1-based result page, default 1, minimum 1.
`Query`	Yes	Business search query, e.g. openai. Required.
`Country`	No	ISO-2 country code, default US, e.g. US.
`PageSize`	No	Results per page, default 20, range 1 to 100.

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.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 structurally. The description adds that results are paginated, which is useful behavioral context, but pagination is already reflected in the Page/PageSize schema fields, so the marginal value beyond structured data is limited.

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 tight sentences, the primary action and scope are front-loaded, and the routing guidance follows immediately. No filler or redundant restatement of the tool name.

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?

An output schema exists, so return-value explanation is unnecessary, and all four parameters are documented in the schema. The description is complete for calling the tool correctly; only minor gaps (e.g., no note on default result ordering or rate limits) keep it from a 5.

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%, documenting Query, Country, Page, and PageSize individually, so the schema carries the load. The description only gestures at 'query and optional country' without adding format or syntax detail beyond the schema, which is the expected baseline when coverage is complete.

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?

The description states a specific verb and resource ('Search Trustpilot business profiles') and adds scope ('by query and optional country, returning paginated results'). It explicitly distinguishes itself from sibling tools by naming trustpilot_business and trustpilot_category_search, so an agent can choose correctly without opening 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 Guidelines4/5

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

It names two concrete alternatives and their selecting conditions: trustpilot_business for a single slug, trustpilot_category_search to browse a category. It doesn't explicitly restate the condition for choosing THIS tool (query-based lookup) but that is strongly implied by 'Search ... by query'.

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?