Skip to main content
Glama
Sign In

ScrapeUnblocker

by com.scrapeunblocker.mcp
OverviewDiscussionsAdmin

Scrape Trustpilot company reviews

trustpilot_reviews
Read-only

Returns a company's Trustpilot profile and reviews as JSON. company is the reviewed domain (e.g. www.nike.com). The response has a company summary (trustScore, totalReviews, ratingDistribution 1-5, categories, contact) and a reviews array - each with url, rating, title, text, verified, verificationLevel, verificationSource, source, pending, merged, author (name, country, review count, id, image, profileUrl, reviewsOfThisCompany), reply (the company's response, with dates) and date / experiencedDate / updatedDate. Page with page/pages (20 reviews per page), and filter with stars, sort (recency/relevancy), language, date, search, verified or replies. Returns JSON. Billed like an API request; listing plugins bill one unit per result page they fetch, so keep max_results modest.

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": {
      "company": "<company>"
    },
    "name": "trustpilot_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOnly reviews from a recent window: last30days, last3months, last6months, last12months. Omit for all time.
pageNo1-based page to start from (20 reviews/page). Default: 1.
sortNoOrdering: recency, relevancy. Default 'recency' (newest first). Default: recency.
pagesNoHow many consecutive pages to fetch from `page` onward (20 reviews each). Stops early at the last page. Default: 1.
starsNoOnly reviews with these star ratings (1, 2, 3, 4, 5). Repeatable, e.g. stars=4&stars=5.
searchNoKeyword to search within the company's reviews.
companyYesThe reviewed company's domain, e.g. 'www.nike.com' or 'nike.com'. A full site URL or a pasted Trustpilot review URL is also accepted.
repliesNoOnly reviews the company has replied to. Default: false.
languageNoReview language ISO-2 code (e.g. 'en', 'de') or 'all'. Default 'all'. Default: all.
verifiedNoOnly verified reviews (Trustpilot's verified badge). Default: false.
proxy_countryNoProxy country the request is sent from (ISO-2, e.g. 'US', 'DE'). Defaults to a country chosen for the site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / pages / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / pages / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / stars / anyOf
      Previous value: -[
-  {
-    "items": {
-      "type": "integer"
-    },
-    "type": "array"
-  },
-  {
-    "$ref": "#/properties/stars/anyOf/0/items"
-  }
-]New value: +[
+  {
+    "items": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "type": "array"
+  },
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  }
+]
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, destructiveHint=false), and the description adds genuinely non-obvious behavior: 20 reviews per page, pages stop early at the last page, proxy country defaults to a country chosen for the site, and per-result-page billing. Minor inconsistency: it advises keeping 'max_results' modest, but no such parameter exists in the schema.

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?

Purpose is front-loaded in the first sentence, and the long field enumeration of the `reviews` array is defensible because no output schema exists. It is still a dense single paragraph with a comma-separated field dump that could be tightened, plus a stray 'max_results' reference that earns no place.

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?

For an 11-parameter scraping tool with no output schema, the description covers return shape, pagination, filters, and cost model well. Gaps are minor: no mention of behavior when a domain has no Trustpilot profile, error/empty-result handling, or whether non-company URLs are resolved.

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 11 parameters are already documented; the description largely restates them (stars, sort, language, date, search, verified, replies, page/pages) rather than adding syntax or edge-case meaning. The only small addition is the example framing of `company` as the reviewed domain, which the schema also provides.

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?

Opens with a specific verb and resource: 'Returns a company's Trustpilot profile and reviews as JSON.' The scope (a single company's profile plus its reviews) is unambiguous and distinguishable from the other review-oriented siblings such as amazon_reviews or youtube_search without inspecting the schema.

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 implied by the content — an agent can infer this is the tool for Trustpilot company reputation data — and the description gives operational advice ('keep max_results modest' due to per-page billing). However, it never states when to prefer this over a generic sibling like browse_page, fetch_html, or search_and_read, nor any exclusions or prerequisites.

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

All ScrapeUnblocker 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