Crawlora MCP

trustpilot_category

Read-only

List businesses in a Trustpilot category by category slug, with page-based results. Use a slug from the category search tool to retrieve businesses for that 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": {
      "Slug": "<Slug>",
      "Page": "<Page>"
    },
    "name": "trustpilot_category"
  }
}

Input Schema

Name	Required	Description	Default
`Page`	Yes	1-based result page, default 1, minimum 1.
`Slug`	Yes	Trustpilot category slug, e.g. software_company.

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

A3.8/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. The description adds that results are page-based (pagination exists), but says nothing about invalid-slug behavior, result limits, or rate limits.

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 tight sentences, with the core action front-loaded and the slug-source hint second. "With page-based results" is mildly redundant against the schema's Page parameter but costs little.

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 values need not be described, and annotations carry the safety profile. The description covers what it returns, how to obtain the slug, and that results are paginated — sufficient for a 2-param read tool.

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

Parameters4/5

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

Schema coverage is 100%, so both parameters are documented, making 3 the baseline. The description adds provenance for the Slug value ("use a slug from the category search tool"), which is meaning the schema itself does not convey.

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 ("List businesses") and resource ("Trustpilot category") with the mechanism ("by category slug"). It implicitly distinguishes itself from the category-listing sibling by naming the "category search tool" as the source of the slug, 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 Guidelines4/5

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

"Use a slug from the category search tool" gives an explicit prerequisite/workflow: obtain the slug first, then call this tool. It does not state when-not to use it or contrast against trustpilot_business_search, so it stops 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?