Skip to main content
Glama
Sign In

scrapeunblocker-mcp-remote

by com.scrapeunblocker
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 rating, title, text, verified, author (name, country, review count), reply (the company's response) and dates. 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.

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.7/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint it adds real behavioral context: a billing model with one unit per fetched page and a caution to keep result counts modest, plus 20 reviews per page and early stop at the last page. It does not state failure modes (unknown domain, missing profile) or rate limits.

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 purpose, then response shape, then pagination/filters, then cost note – a logical order with mostly dense phrasing. Minor waste: 'Returns JSON' appears twice, and the parameter list reads as a schema recap.

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, the description usefully enumerates the response envelope (company summary fields and per-review fields including reply and dates), which is what an agent needs to decide whether to call it. It leaves only error behavior and the proxy parameter unaddressed.

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 every parameter is already documented, and the description largely restates them (page/pages, stars, sort, language, date, search, verified, replies) with a little added context like '20 reviews per page'. proxy_country, the one parameter with non-obvious semantics, is not mentioned at all.

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?

Description opens with a specific verb and resource: returns a company's Trustpilot profile and reviews, keyed on the reviewed domain. It is clearly distinguishable from generic fetch/scrape siblings, though it never names an alternative source tool to contrast with.

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?

It explains use of pagination and filters and gives a cost warning about keeping max_results modest, implying when to page deep versus just take the summary. There is no explicit when-to-use/when-not guidance or comparison to sibling review tools such as amazon_reviews.

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

All scrapeunblocker-mcp-remote toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources