MCP + API · kestrel/tripadvisor-reviews-scraper

TripAdvisor Reviews Scraper & API: Hotel Reviews, Guest Reviews

TripAdvisor hotel reviews and TripAdvisor ratings by URL, id or name. One row per review: bubbles, title, text, six sub-ratings, stay date, trip type, reviewer, photos, management response. Free hotel row: rating, review count, city ranking. Filters: negative reviews, new reviews only. 24 languages.

Open Actor Download MCP config

Connect this tool

Add this URL as a remote MCP server in your client, then sign in to Apify. For a client-specific setup, use Apify's configurator.

https://mcp.apify.com?tools=call-actor,fetch-actor-details,kestrel/tripadvisor-reviews-scraper
Generic MCP client configuration
{
  "mcpServers": {
    "kestrel-tripadvisor-reviews-scraper": {
      "url": "https://mcp.apify.com?tools=call-actor,fetch-actor-details,kestrel/tripadvisor-reviews-scraper"
    }
  }
}

Understand the output before you run

One row per guest review (charged), plus a free hotel context row and a free status row per hotel and language.

Declared dataset fields and row types · Output locations and dataset links

Use the declared dataset schema for item fields; the output schema describes where results are stored. Optional fields may be null or absent. If an integration shows a sampled schema without an optional field, check this declaration, the Actor instructions and actual returned rows before concluding that the field is unsupported.

Inspect 57 declared output fields
FieldTypeMeaning
typestringreview | hotel | status
targetstring / nullThe input value (URL, id or name) this row came from
location_idstring / nullTripAdvisor's numeric location id (the d<number> in its URLs)
geo_idstring / nullTripAdvisor's numeric geo id of the hotel's city (the g<number> in its URLs)
hotel_namestring / nullHotel name as the review page shows it
languagestring / nullSite language the row was read in (en = tripadvisor.com, de = tripadvisor.de, …)
review_idstring / nullTripAdvisor's numeric review id
original_languagestring / nullLanguage the review was written in
translatedboolean / nulltrue when the text is a machine translation into the site language
titlestring / nullReview title
textstring / nullFull review text
ratingnumber / null1-5 bubbles on review rows; the hotel's overall bubble rating (e.g. 4.7) on hotel rows
sub_ratingsobject / nullBubbles per aspect the reviewer rated: value, rooms, location, cleanliness, service, sleep_quality
review_datestring / nullDate the review was posted, YYYY-MM-DD
created_datestring / nullDate the review was written, YYYY-MM-DD
stay_datestring / nullMonth of the stay as TripAdvisor records it, YYYY-MM-DD
trip_typestring / nullFAMILY | COUPLES | SOLO | BUSINESS | FRIENDS | null
helpful_votesinteger / nullHelpful votes the review received
reviewer_namestring / nullReviewer display name
reviewer_usernamestring / nullReviewer profile handle
reviewer_verifiedboolean / nullWhether TripAdvisor marks the reviewer as verified
reviewer_contributionsinteger / nullReviewer's total contributions on TripAdvisor
reviewer_helpful_votesinteger / nullHelpful votes across all of the reviewer's contributions
reviewer_hometownstring / nullReviewer hometown as shown, e.g. "Brooklyn, New York"
photosarray / nullPhoto URLs attached to the review (1200 px renditions)
photo_countinteger / nullHow many photos the review carries
responsestring / nullThe property's management response text, if any
response_datestring / nullDate of the management response, YYYY-MM-DD
response_idstring / nullTripAdvisor's id of the management response
urlstring / nullDirect URL of the review page (review rows) or of the hotel review page (hotel rows)
hotel_urlstring / nullThe hotel's canonical review page on the site the row was read from
review_countinteger / nullTotal reviews the hotel has across all languages
rating_countsobject / nullReviews per bubble rating, keys "1"…"5"
reviews_by_languageobject / nullReviews per language, e.g. {"en": 1393, "fr": 220}
rankingstring / nullTripAdvisor ranking sentence, e.g. "#33 of 372 hotels in Lisbon"
ranking_positioninteger / nullRank position in the city
ranking_ofinteger / nullNumber of hotels ranked in the city
addressstring / nullStreet address
citystring / nullCity
postal_codestring / nullPostal code
country_codestring / nullISO country code
latitudenumber / nullLatitude
longitudenumber / nullLongitude
phonestring / nullPhone as listed
websitestring / nullOfficial website as listed
price_rangestring / nullTripAdvisor price band, e.g. "$$"
amenitiesarray / nullAmenity names TripAdvisor lists
reviews_listedinteger / nullReviews the site lists for the hotel in this language (translations included)
reviews_fetchedinteger / nullReviews read in this run for the hotel and language before filters
statusstring / nullok | no_reviews | not_found | duplicate | error (status rows)
reviewsinteger / nullReviews delivered for this hotel and language (status rows)
filteredinteger / nullReviews dropped by the filters, never charged (status rows)
pagesinteger / nullReview pages read (status rows)
totalinteger / nullReviews the site lists in this language (status rows)
duplicatesinteger / null1 when this target resolved to a hotel another target already covers (status rows)
errorstring / nullWhy a target failed (status rows)
fetched_atstring / nullUTC timestamp of the request

Start with a small sample

Use call-actor with the JSON below. The $0.25 run ceiling is separate from the Actor input and may stop the sample early. Change the target to match your request. This input validates against build 1.2.5; it is not a promise that the source has matching rows today.

{
  "actor": "kestrel/tripadvisor-reviews-scraper",
  "input": {
    "startUrls": [
      "https://www.tripadvisor.com/Hotel_Review-g189158-d4509998-Reviews-Memmo_Alfama_Hotel-Lisbon_Lisbon_District_Central_Portugal.html"
    ],
    "languages": [
      "en"
    ],
    "maxReviewsPerHotel": 3
  },
  "callOptions": {
    "maxTotalChargeUsd": 0.25,
    "timeout": 300
  },
  "waitSecs": 30
}

After completion, use get-dataset-items with storages.datasets.default.id. If still running, poll get-actor-run using the returned runId. Check status rows and errors before treating an empty dataset as no matches.

Call from Python, JavaScript or REST

Python SDK 3 example · JavaScript SDK 2 example · curl + jq example. Each uses this same small input, reads APIFY_TOKEN from your environment, sets a five-minute run timeout and exports all dataset row types as JSON Lines. The $0.25 run ceiling is separate from the Actor input and may stop the sample early. Inspect the run and source status before treating results as complete. Installation and usage.

Pricing and limits

Current listed event prices in USD. Some Actors charge for successful source checks even when no output rows match. The event descriptions below define those differences.

EventUSD eachWhat is charged
review$0.005One TripAdvisor hotel review: 1-5 bubbles, six sub-ratings, management response (row keys review_id, rating, title, text, sub_ratings, language, original_language, stay_date, trip_type, reviewer_name, photos, helpful_votes, response): $5 per 1,000 reviews, once per language site; maxReviewsPerHotel 100 (default) caps a hotel at $0.50 per language. Not charged: the hotel row (rating, review count, city ranking, address, amenities), reviews removed by maxRating, tripTypes, sinceDate, requireText or includeTranslated, hotels with no reviews, unknown ids, duplicate targets, failed pages and status rows. No start fee; proxy and compute are included in the event price. The run stops at the maximum cost per run you set when starting it (Apify run option maxTotalChargeUsd), never above it.

Contracts for agents

Public contract checked 2026-11-11. Active build: 1.2.5. Refresh live details before a large or recurring run.