Rowfeed Search & Market Data

rowfeed/tripadvisor-reviews-scraper

rowfeed--tripadvisor-reviews-scraper

Destructive

This tool calls the Actor "rowfeed/tripadvisor-reviews-scraper" and retrieves its output results. Actor description: Export the newest or most detailed Tripadvisor reviews of any hotel, restaurant or attraction: rating, title, text, date, visit month, language, reviewer country and owner reply, plus the place's rating and star breakdown. Paste Tripadvisor links. About $0.50 per 1,000 reviews.

Input Schema

Name	Required	Description	Default
`places`	No	One Tripadvisor link per line: a hotel, restaurant, attraction, tour or vacation rental page on any Tripadvisor country site (open the place on Tripadvisor and copy the address). Up to 500 per run. Example values: ["https://www.tripadvisor.com/Hotel_Review-g186338-d187686-Reviews-The_Savoy-London_England.html"]
`sortBy`	No	Which reviews come first: the newest, or the most detailed (Tripadvisor's own order). 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.
`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 place, in the chosen order. Up to 500 per run. Places 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 6, 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"
+    },
+    "from_snapshot": {
+      "type": "boolean"
+    },
+    "language": {
+      "type": "string"
+    },
+    "original_language": {
+      "type": "string"
+    },
+    "owner_replied_at": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "owner_reply": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "photos_count": {
+      "type": "number"
+    },
+    "place_name": {
+      "type": "string"
+    },
+    "place_rating": {
+      "type": "number"
+    },
+    "place_rating_distribution": {
+      "properties": {
+        "1": {
+          "type": "number"
+        },
+        "2": {
+          "type": "number"
+        },
+        "3": {
+          "type": "number"
+        },
+        "4": {
+          "type": "number"
+        },
+        "5": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "place_reviews_total": {
+      "type": "number"
+    },
+    "place_type": {
+      "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": [
+        "null",
+        "string"
+      ]
+    },
+    "sort": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "tripadvisor_url": {
+      "type": "string"
+    },
+    "visit_month": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 6, 2026

addedInput schema / properties / places / prefill

Added value: +[
+  "https://www.tripadvisor.com/Hotel_Review-g186338-d187686-Reviews-The_Savoy-London_England.html"
+]

Changed1 schema field 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."

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"
-    },
-    "from_snapshot": {
-      "type": "boolean"
-    },
-    "language": {
-      "type": "string"
-    },
-    "original_language": {
-      "type": "string"
-    },
-    "owner_replied_at": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "owner_reply": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "photos_count": {
-      "type": "number"
-    },
-    "place_name": {
-      "type": "string"
-    },
-    "place_rating": {
-      "type": "number"
-    },
-    "place_rating_distribution": {
-      "properties": {
-        "1": {
-          "type": "number"
-        },
-        "2": {
-          "type": "number"
-        },
-        "3": {
-          "type": "number"
-        },
-        "4": {
-          "type": "number"
-        },
-        "5": {
-          "type": "number"
-        }
-      },
-      "type": "object"
-    },
-    "place_reviews_total": {
-      "type": "number"
-    },
-    "place_type": {
-      "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": [
-        "null",
-        "string"
-      ]
-    },
-    "sort": {
-      "type": "string"
-    },
-    "title": {
-      "type": "string"
-    },
-    "tripadvisor_url": {
-      "type": "string"
-    },
-    "visit_month": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

Changed1 schema field changedNov 5, 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"
+    },
+    "from_snapshot": {
+      "type": "boolean"
+    },
+    "language": {
+      "type": "string"
+    },
+    "original_language": {
+      "type": "string"
+    },
+    "owner_replied_at": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "owner_reply": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "photos_count": {
+      "type": "number"
+    },
+    "place_name": {
+      "type": "string"
+    },
+    "place_rating": {
+      "type": "number"
+    },
+    "place_rating_distribution": {
+      "properties": {
+        "1": {
+          "type": "number"
+        },
+        "2": {
+          "type": "number"
+        },
+        "3": {
+          "type": "number"
+        },
+        "4": {
+          "type": "number"
+        },
+        "5": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "place_reviews_total": {
+      "type": "number"
+    },
+    "place_type": {
+      "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": [
+        "null",
+        "string"
+      ]
+    },
+    "sort": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "tripadvisor_url": {
+      "type": "string"
+    },
+    "visit_month": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedNov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations flag destructiveHint=true and openWorldHint=true, and the description adds the two pieces of context that matter most for that risk profile: per-review cost (~$0.50 per 1,000) and the paid-plan requirement for live lookups. It still doesn't explain the asynchronous Actor-run semantics in the description body (that lives only in the waitSecs parameter text) or what 'destructive' means here beyond spending money.

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 with little waste, and the resource and return fields are front-loaded before the pricing note. The opening boilerplate about calling the Actor and retrieving its output results is framing rather than information, but it is brief enough not to hurt.

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 and all six parameters fully documented in the schema, the description only needs to establish purpose, cost and access constraints, which it does. The remaining gap is behavioral: the polling/terminal-state lifecycle is documented in the waitSecs parameter rather than the description, which is acceptable given the structured coverage.

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 explains places, sortBy, maxReviews, newerThan, onlyWithText and waitSecs in detail. The description adds almost no parameter meaning beyond echoing 'newest or most detailed' for the sort order; the billing-per-review note is the only increment.

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 states a specific verb and resource: exporting Tripadvisor reviews for hotels, restaurants or attractions, and enumerates the returned fields (rating, title, text, date, visit month, language, reviewer country, owner reply, star breakdown). The Tripadvisor scope implicitly distinguishes it from siblings like google-maps-reviews-scraper and trustpilot-reviews-scraper, but those alternatives are never named, so the differentiation is left to inference.

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 only implied: 'Paste Tripadvisor links' tells the agent the input form, and the pricing line ('About $0.50 per 1,000 reviews') plus the schema note about a paid Apify plan give cost context. There is no explicit when-to-use/when-not statement and no routing to the alternative review scrapers in the sibling set.

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/tripadvisor-reviews-scraper

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources