mcp-review-platform-reputation-enricher

Get Trustpilot Reputation

get_trustpilot_reputation

Read-onlyIdempotent

Resolve a company domain to its Trustpilot TrustScore, review count, star score, claimed status, and categories. Returns one flat row for Clay enrichment using your own Trustpilot API key.

Instructions

Resolve a company domain to its Trustpilot business unit and return the TrustScore, review count, star score, claimed and verified status and categories, through Trustpilot's documented Business Units API. Returns one flat Clay ready row. Requires the CALLER's own Trustpilot API key; without one every row reports skipped rather than pretending to have looked. A refused request reports blocked and a domain with no business unit reports not_found, and those two are never conflated. G2, Capterra and Glassdoor ship as skipped status columns so the row shape does not change when a source is added. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.

Input Schema

TableJSON Schema

Name	Required	Description
`sources`	No	Which review sources to query. v1 serves Trustpilot only. G2, Capterra and Glassdoor appear as columns and always report skipped, with the reason on the row, because all three refused every documented route and none publishes an API we can use as documented. This setting exists so a saved configuration keeps working when a source is added. Sent as a string for Clay compatibility.
`skipCache`	No	When "false" (default) a successful lookup is cached for seven days and reused, which costs you nothing on a repeated run. Set "true" to force a fresh fetch. Sent as a string for Clay compatibility.
`company_name`	No	Optional. Carried through to the output row for joining. The Trustpilot lookup is keyed on the domain, so the name does not change which business unit is returned.
`company_domain`	No	Bare company domain, for example stripe.com. Trustpilot business units are keyed on the company website domain, so this is the correct and only lookup key.
`minReviewCount`	No	Sets rating_is_meaningful on the row. A 5.0 rating from two reviews and a 4.2 from nine hundred are not comparable numbers, and this is the column that says which one you are looking at. It never drops a row and never changes the rating returned. Sent as a string for Clay compatibility.
`trustpilotApiKey`	No	YOUR OWN Trustpilot API key, free to create at developers.trustpilot.com. REQUIRED: the Business Units API is not open, so without a key this actor reports skipped rather than guessing. Marked secret, so the value never renders on this page.
`includeCategories`	No	When "true" (default) the Trustpilot categories the business is listed under are returned. They are a useful cheap proxy for what a company actually sells, which is often not what its homepage says. Sent as a string for Clay compatibility.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses failure modes ('blocked' vs 'not_found' are never conflated), the skipped behavior without an API key, stable row shape across sources, and Apify credit consumption. This gives the agent accurate expectations for side effects and error handling.

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?

The description is front-loaded with the primary function, then moves to output shape, prerequisites, error semantics, and cost. Each sentence carries distinct information and the length is justified by the tool's nuanced behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description supplies the return shape and key statuses, while the input schema handles parameter details. The combination fully covers expected inputs, outputs, failure states, and operational requirements for an agent to invoke it correctly.

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?

The input schema already covers all seven parameters with 100% description coverage, so the description does not need to repeat parameter details. It adds only high-level context (e.g., API key requirement and source limitations) rather than new per-parameter semantics, which keeps it at the baseline 3.

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 opens with a specific verb+resource: 'Resolve a company domain to its Trustpilot business unit' and enumerates returned fields (TrustScore, review count, star score, claimed/verified status, categories). It also adds the output shape ('one flat Clay ready row'), so an agent knows exactly what this tool produces.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Although there are no sibling tools, the description gives clear when-to-use context: it is for Trustpilot reputation from a domain, and it explicitly says G2, Capterra and Glassdoor are not queried and always report skipped. It also sets the prerequisite of the caller's own Trustpilot API key and warns that without one rows report skipped.

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

get_trustpilot_reputationA