Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

trustpilot_business

Retrieve a Trustpilot business profile by slug via Crawlora MCP to view trust score, reviews, categories, contact details, and verification status.

Instructions

Get Trustpilot business profile. Returns a Trustpilot business profile by slug, such as openai.com. The profile has the name, trust_score, review_count, rating histogram, review summary and topics, categories, claimed status, website URL, reply metrics, company activity and verification flags, and an about section with description and contact details.

Input Schema

NameRequiredDescriptionDefault
slugYesTrustpilot business slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It thoroughly describes what the profile contains, which is genuinely useful, but says nothing about behavioral traits such as error/not-found behavior, rate limits, or freshness of the trust score. It discloses content, not operation semantics.

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 purpose sentence, then the return-field enumeration. The long list of profile fields is dense but each item is informative rather than padding, so it earns its length reasonably well.

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?

No output schema exists, so the description compensates by enumerating the returned fields (trust_score, review_count, histogram, topics, verification flags, about section, etc.). For a simple one-parameter lookup this leaves the agent well-equipped, though it omits any failure-mode or auth context.

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% and the schema already labels the field 'Trustpilot business slug', so baseline is 3. The description adds real value by supplying the concrete example format `openai.com`, which tells the agent what a valid slug looks like beyond the bare schema text.

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?

The description opens with a specific verb and resource ('Get Trustpilot business profile') and immediately pins the retrieval key ('by `slug`, such as `openai.com`'). It is clear what the tool does, though it never names sibling tools like trustpilot_business_search or trustpilot_business_reviews to differentiate the entry point from search/review lookups.

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?

Usage is only implied: pass a slug, get the profile. There is no explicit when-to-use statement, no condition selecting it over the search or reviews siblings, and no note about what to do if the slug is unknown (use search first). Adequate but with a clear gap.

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