Rowfeed Search & Market Data

rowfeed/trustpilot-reviews-scraper

rowfeed--trustpilot-reviews-scraper

Destructive

This tool calls the Actor "rowfeed/trustpilot-reviews-scraper" and retrieves its output results. Actor description: Export the newest or most relevant Trustpilot reviews of any company: star rating, title, full text, date, language, verified flag, reviewer country and company reply, plus the company's TrustScore and review count. Paste Trustpilot links, websites or domains. About $0.25 per 1,000 reviews.

Input Schema

Name	Required	Description	Default
`sortBy`	No	Which reviews come first: the newest, or the most relevant (Trustpilot's default). Example values: "newest"	newest
`waitSecs`	No	Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
`companies`	No	One company per line: its Trustpilot page (any country site, e.g. https://www.trustpilot.com/review/www.booking.com), its website, or just its domain (booking.com). Up to 500 per run. Example values: ["https://www.trustpilot.com/review/www.booking.com"]
`newerThan`	No	Leave out older reviews: a date (2026-10-01) or an age (7 days, 2 weeks, 3 months). Left-out reviews are not charged. With "Newest first", no further reviews are fetched once the cutoff is reached, which makes scheduled monitoring cheap.
`maxReviews`	No	How many reviews to get per company, in the chosen order. Up to 200 (the most Trustpilot's data provider returns per company). Companies with fewer reviews only pay for what they have. Example values: 20
`onlyWithText`	No	Leave out reviews that have no text. Left-out reviews are not charged.

Output Schema

Name	Required	Description
`tip`	No	Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
`runId`	Yes	Actor run ID
`stats`	No	Run statistics
`status`	Yes	Run status: READY \| RUNNING \| TIMING-OUT \| TIMED-OUT \| ABORTING \| ABORTED \| SUCCEEDED \| FAILED
`actorId`	Yes	Stable Apify Actor ID from the run record
`summary`	Yes	Past-tense summary of the run state
`exitCode`	No	Actor process exit code; populated for terminal states (especially FAILED)
`nextStep`	Yes	One primary follow-up action with identifiers interpolated
`storages`	Yes	Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
`actorName`	No	"username/actor-name"
`startedAt`	No	ISO timestamp when the run started
`finishedAt`	No	ISO timestamp when the run finished (terminal states only)
`statusMessage`	No	Pass-through from Apify run.statusMessage
`apifyConsoleUrl`	No	Personalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Added value: +{
+  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
+  "properties": {
+    "checked_at": {
+      "type": "string"
+    },
+    "company_address": {
+      "type": "string"
+    },
+    "company_name": {
+      "type": "string"
+    },
+    "company_rating": {
+      "type": "number"
+    },
+    "company_replied_at": {
+      "type": "null"
+    },
+    "company_reply": {
+      "type": "null"
+    },
+    "company_reviews_total": {
+      "type": "number"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "from_snapshot": {
+      "type": "boolean"
+    },
+    "language": {
+      "type": "string"
+    },
+    "position": {
+      "type": "number"
+    },
+    "published_at": {
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "rating": {
+      "type": "number"
+    },
+    "review_id": {
+      "type": "string"
+    },
+    "review_text": {
+      "type": "string"
+    },
+    "review_url": {
+      "type": "string"
+    },
+    "reviewer_country": {
+      "type": "string"
+    },
+    "sort": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "trustpilot_url": {
+      "type": "string"
+    },
+    "verified": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedNov 6, 2026

addedInput schema / properties / companies / prefill

Added value: +[
+  "https://www.trustpilot.com/review/www.booking.com"
+]

removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Removed value: -{
-  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
-  "properties": {
-    "checked_at": {
-      "type": "string"
-    },
-    "company_address": {
-      "type": "string"
-    },
-    "company_name": {
-      "type": "string"
-    },
-    "company_rating": {
-      "type": "number"
-    },
-    "company_replied_at": {
-      "type": "null"
-    },
-    "company_reply": {
-      "type": "null"
-    },
-    "company_reviews_total": {
-      "type": "number"
-    },
-    "domain": {
-      "type": "string"
-    },
-    "from_snapshot": {
-      "type": "boolean"
-    },
-    "language": {
-      "type": "string"
-    },
-    "position": {
-      "type": "number"
-    },
-    "published_at": {
-      "type": "string"
-    },
-    "query": {
-      "type": "string"
-    },
-    "rating": {
-      "type": "number"
-    },
-    "review_id": {
-      "type": "string"
-    },
-    "review_text": {
-      "type": "string"
-    },
-    "review_url": {
-      "type": "string"
-    },
-    "reviewer_country": {
-      "type": "string"
-    },
-    "sort": {
-      "type": "string"
-    },
-    "title": {
-      "type": "string"
-    },
-    "trustpilot_url": {
-      "type": "string"
-    },
-    "verified": {
-      "type": "boolean"
-    }
-  },
-  "type": "object"
-}

Changed2 schema fields changedNov 6, 2026

addedInput schema / description

Added value: +"Live lookups need a paid Apify plan (any plan). The pre-filled example works on the free plan."

addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Added value: +{
+  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
+  "properties": {
+    "checked_at": {
+      "type": "string"
+    },
+    "company_address": {
+      "type": "string"
+    },
+    "company_name": {
+      "type": "string"
+    },
+    "company_rating": {
+      "type": "number"
+    },
+    "company_replied_at": {
+      "type": "null"
+    },
+    "company_reply": {
+      "type": "null"
+    },
+    "company_reviews_total": {
+      "type": "number"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "from_snapshot": {
+      "type": "boolean"
+    },
+    "language": {
+      "type": "string"
+    },
+    "position": {
+      "type": "number"
+    },
+    "published_at": {
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "rating": {
+      "type": "number"
+    },
+    "review_id": {
+      "type": "string"
+    },
+    "review_text": {
+      "type": "string"
+    },
+    "review_url": {
+      "type": "string"
+    },
+    "reviewer_country": {
+      "type": "string"
+    },
+    "sort": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "trustpilot_url": {
+      "type": "string"
+    },
+    "verified": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 5, 2026

removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Removed value: -{
-  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
-  "properties": {
-    "checked_at": {
-      "type": "string"
-    },
-    "company_address": {
-      "type": "string"
-    },
-    "company_name": {
-      "type": "string"
-    },
-    "company_rating": {
-      "type": "number"
-    },
-    "company_replied_at": {
-      "type": "null"
-    },
-    "company_reply": {
-      "type": "null"
-    },
-    "company_reviews_total": {
-      "type": "number"
-    },
-    "domain": {
-      "type": "string"
-    },
-    "from_snapshot": {
-      "type": "boolean"
-    },
-    "language": {
-      "type": "string"
-    },
-    "position": {
-      "type": "number"
-    },
-    "published_at": {
-      "type": "string"
-    },
-    "query": {
-      "type": "string"
-    },
-    "rating": {
-      "type": "number"
-    },
-    "review_id": {
-      "type": "string"
-    },
-    "review_text": {
-      "type": "string"
-    },
-    "review_url": {
-      "type": "string"
-    },
-    "reviewer_country": {
-      "type": "string"
-    },
-    "sort": {
-      "type": "string"
-    },
-    "title": {
-      "type": "string"
-    },
-    "trustpilot_url": {
-      "type": "string"
-    },
-    "verified": {
-      "type": "boolean"
-    }
-  },
-  "type": "object"
-}

Changed1 schema field changedNov 4, 2026

addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Added value: +{
+  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
+  "properties": {
+    "checked_at": {
+      "type": "string"
+    },
+    "company_address": {
+      "type": "string"
+    },
+    "company_name": {
+      "type": "string"
+    },
+    "company_rating": {
+      "type": "number"
+    },
+    "company_replied_at": {
+      "type": "null"
+    },
+    "company_reply": {
+      "type": "null"
+    },
+    "company_reviews_total": {
+      "type": "number"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "from_snapshot": {
+      "type": "boolean"
+    },
+    "language": {
+      "type": "string"
+    },
+    "position": {
+      "type": "number"
+    },
+    "published_at": {
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "rating": {
+      "type": "number"
+    },
+    "review_id": {
+      "type": "string"
+    },
+    "review_text": {
+      "type": "string"
+    },
+    "review_url": {
+      "type": "string"
+    },
+    "reviewer_country": {
+      "type": "string"
+    },
+    "sort": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "trustpilot_url": {
+      "type": "string"
+    },
+    "verified": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 4, 2026

removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Removed value: -{
-  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
-  "properties": {
-    "checked_at": {
-      "type": "string"
-    },
-    "company_address": {
-      "type": "string"
-    },
-    "company_name": {
-      "type": "string"
-    },
-    "company_rating": {
-      "type": "number"
-    },
-    "company_replied_at": {
-      "type": "null"
-    },
-    "company_reply": {
-      "type": "null"
-    },
-    "company_reviews_total": {
-      "type": "number"
-    },
-    "domain": {
-      "type": "string"
-    },
-    "from_snapshot": {
-      "type": "boolean"
-    },
-    "language": {
-      "type": "string"
-    },
-    "position": {
-      "type": "number"
-    },
-    "published_at": {
-      "type": "string"
-    },
-    "query": {
-      "type": "string"
-    },
-    "rating": {
-      "type": "number"
-    },
-    "review_id": {
-      "type": "string"
-    },
-    "review_text": {
-      "type": "string"
-    },
-    "review_url": {
-      "type": "string"
-    },
-    "reviewer_country": {
-      "type": "string"
-    },
-    "sort": {
-      "type": "string"
-    },
-    "title": {
-      "type": "string"
-    },
-    "trustpilot_url": {
-      "type": "string"
-    },
-    "verified": {
-      "type": "boolean"
-    }
-  },
-  "type": "object"
-}

AddedNov 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare openWorldHint=true and destructiveHint=true, and the description usefully adds the cost model (~$0.25 per 1,000 reviews) and the paid-plan prerequisite for live lookups. However, it never acknowledges that invoking it creates an Actor run with side effects and possible cost, nor how partial/long runs are handled — those mechanics only appear inside the waitSecs parameter description.

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?

Two sentences, front-loaded with the scope and then the returned fields and pricing. The opening 'calls the Actor ... and retrieves its output results' is harness boilerplate rather than tool-specific information, but overall it is tight with no filler.

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 an output schema present, the description needn't explain return shape, and it covers inputs, breadth limits, pricing, and plan requirements well. The remaining gap is the run lifecycle and destructive side effects, which an agent would want before firing a paid, write-like operation.

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 the schema already carries full parameter meaning including the sortBy enum, the 0–45 waitSecs cap, the 500-company limit, and the 200-review cap. The description repeats the accepted company input formats but adds nothing beyond what the schema states; baseline 3 applies.

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 gives a specific verb and resource — exports Trustpilot reviews for a company — and enumerates the returned fields (star rating, title, text, date, verified flag, reply, TrustScore). It is clearly distinguishable from siblings like tripadvisor-reviews-scraper or google-maps-reviews-scraper by the platform named, though it never explicitly contrasts with them.

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 context is implied through the accepted input forms (Trustpilot page, website, or bare domain) and the note that live lookups require a paid Apify plan. There is no explicit statement of when to choose this over the other review scrapers in the sibling list, nor any when-not guidance.

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

All Rowfeed Search & Market Data tools Inspect

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.

rowfeed/trustpilot-reviews-scraper

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources