Skip to main content
Glama

Visibility Genies

Get Trustpilot reviews

get_trustpilot_reviews

Collects Trustpilot reviews for one company, with rating, author, verified status, text, and whether the company replied. Use it for review-gap analysis against competitors and to spot unanswered reviews; find the company's Trustpilot domain with search_trustpilot_businesses first. Usually completes within this call; if the queued job is still running you get status 'processing' plus a taskId, so call again with that taskId in 30-60 seconds to collect the result at no extra cost. Estimated price: $0.01 for 20 reviews, billed per 20 at twice the Local page's normal-priority rate, so the call usually returns them; reviews bought within a day, here or on the Local page, are answered at no charge. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_trustpilot_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoNumber of reviews to collect (20-200). Defaults to 20. Billed per 20 reviews.
domainNoThe company's domain as Trustpilot lists it: the domain in search_trustpilot_businesses rows, or the part after trustpilot.com/review/ (e.g. www.example.com). Required unless resuming with taskId.
sortByNoReview sort order. Defaults to recency (newest first).
taskIdNoResume a previous call that returned status "processing". Pass back the taskId exactly as returned (format "trustpilot_reviews:<id>"). Resuming charges no extra credits.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
statusYes
taskIdYes
totalsNo
reviewsNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses the paid-credit model ($0.01 per 20 reviews), the auto-approved spend ceiling, the pre-purchase refusal path and how to recover with approvedMaxCostUsd, and the async 'processing' + taskId resume flow with the 30-60 second retry interval at no extra cost. That is exactly the financial and asynchronous behavior an agent cannot infer from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, which is good, but the remaining text is one dense block with comma splices and a hard-to-parse clause ('reviews bought within a day, here or on the Local page, are answered at no charge') that references a 'Local page' never defined in this definition. The pricing/spend-limit material is genuinely needed but could be split into short bullets.

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?

For a tool with a heavy operational profile (paid credits, spend-limit refusal, async polling), all the decision-critical facts are present: prerequisite lookup, retry timing, billing unit, and the approval escape hatch. Return-shape detail is rightly omitted because an output schema exists.

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 the baseline is 3, but the description goes past the schema on the two riskiest parameters: it explains where the domain value comes from (the search_trustpilot_businesses row or the part after trustpilot.com/review/) and frames approvedMaxCostUsd as a user-approval gate that must never be set unprompted. The depth-to-cost relationship ('billed per 20') is also restated in context, though sortBy gets no added meaning.

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 first sentence gives a specific verb and resource ('Collects Trustpilot reviews for one company') plus exactly what each review record contains (rating, author, verified status, text, company reply). That distinguishes it from the sibling search_trustpilot_businesses (which finds the company) without ambiguity.

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?

It states clear use cases ('review-gap analysis against competitors', 'spot unanswered reviews') and a hard prerequisite: resolve the domain via search_trustpilot_businesses first. What's missing is any disambiguation from other review-retrieval siblings such as get_business_reviews or get_tripadvisor_reviews, so the agent must infer which review source to pick.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources