Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

trustpilot_category

Retrieve a Trustpilot category by slug and list its companies with trust scores, reviews, contact details, and pagination.

Instructions

Get Trustpilot category detail. Returns a Trustpilot category by slug (for example software_company), with the companies listed on one page; page is 1-based and defaults to 1. Each company has its display name, identifying_name, trust_score, stars, review_count, location, contact details, categories and Trustpilot URL. Also returns breadcrumbs, newest companies and pagination.has_next_page.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number; defaults to 1
slugYesTrustpilot category slug

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, the description carries the full burden, and it does well: it discloses the pagination model (1-based `page`, defaults to 1) and enumerates the returned company fields plus breadcrumbs, newest companies, and `pagination.has_next_page`. It does not state auth or rate-limit behavior, but for a read-only lookup the disclosure is solid.

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 purpose in the first sentence, followed by parameter behavior and response shape. The field enumeration is long but each item (trust_score, review_count, pagination) earns its place since no output schema exists.

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?

With no output schema and no annotations, the description compensates by describing the full response shape and pagination. The only real gap is guidance on discovering valid slugs, which sibling category tools presumably cover.

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 coverage is 100%, so the baseline is 3. The description reinforces `page` as 1-based with a default and supplies a concrete slug example (`software_company`), adding some meaning beyond the schema's terse 'Trustpilot category slug'.

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 and resource ('Get Trustpilot category detail. Returns a Trustpilot category by `slug`'), so the agent knows it fetches a single category rather than listing or searching them. It does not explicitly name the near-identical siblings (trustpilot_categories, trustpilot_category_search), so it stops short of full differentiation.

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?

The example slug (`software_company`) implies how to call it, but there is no explicit when-to-use versus trustpilot_categories or trustpilot_category_search, and no note on how to obtain a slug. Usage is implied rather than stated.

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