Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

trustpilot_category_search

Read-only

Search Trustpilot categories by query, optionally scoped by country and locale. Results include matching category names and slugs; use a returned slug to list businesses in the 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_category_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
SizeNoMaximum number of categories, default 20, range 1 to 100.
QueryYesCategory search query, e.g. openai. Required.
LocaleNoLocale in ll-CC format, default en-US, e.g. en-US.
CountryNoISO-2 country code, default US, e.g. US.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 agent knows this is a safe, open-web read. The description adds that results include names and slugs and that slugs feed into a downstream listing tool, which is useful context. However, it doesn't mention pagination, rate limits, or result ordering beyond the schema's Size parameter.

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 sentences, zero waste, front-loaded with the core action and scope. The second sentence efficiently conveys the practical follow-up step without redundancy.

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?

Complete for a read-only category search with an output schema. The description covers purpose, scope, and the key output element (slug) needed for chain calls. Minor gap: it doesn't note result shape limitations or caveats, but the output schema likely covers return values.

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 (Query, Country, Locale, Size) are already fully documented with types, defaults, and formats. The description adds no parameter-specific syntax or examples beyond what the schema provides, so 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?

States a specific verb+resource ('Search Trustpilot categories') and the search scope (by query, optionally scoped by country and locale). Distinguishable from siblings like trustpilot_categories (list all) and trustpilot_category (single fetch) 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?

Provides a clear usage path: search for categories, then use a returned slug to list businesses in the category. This implies when to use it versus direct lookup tools, though it doesn't explicitly name the sibling tools to avoid (e.g., trustpilot_categories) or state when not to use it.

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

All Crawlora MCP toolsInspect
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