MCP + API · kestrel/trip-com-reviews-scraper
Trip.com Reviews Scraper — Ctrip Hotel Guest Reviews & Ratings
Trip.com and Ctrip (携程) hotel guest reviews by URL or id. One row per review: 0-10 rating, 4 sub-scores, text, stay date, room, travel type, reviewer country, photos, hotel reply, source. Free hotel row: stars, address, scores. Filters before billing: language, max score (negative reviews). 酒店点评
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/trip-com-reviews-scraper
Generic MCP client configuration
{
"mcpServers": {
"kestrel-trip-com-reviews-scraper": {
"url": "https://mcp.apify.com?tools=call-actor,fetch-actor-details,kestrel/trip-com-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 property.
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 50 declared output fields
| Field | Type | Meaning |
|---|---|---|
type | string | Row type: review, hotel or status. |
hotel_id | string / null | Trip.com's numeric hotel id. |
hotel_name | string / null | Hotel name, from the hotel page (hotel rows and, when the page was read, review rows). |
url | string / null | The Trip.com hotel page, when the run was given one. |
locale | string / null | Trip.com locale the request used. |
stars | integer / null | Hotel rows: star class. |
address | string / null | Hotel rows: street address. |
city | string / null | Hotel rows: city. |
country | string / null | Hotel rows: country. |
review_count | integer / null | Hotel rows: how many reviews Trip.com shows for the property. |
languages | array / null | Hotel rows: the languages the property's reviews come in, with Trip.com's id and count for each. |
travel_types | array / null | Hotel rows: traveler types with review counts. |
reviews_fetched | integer / null | Hotel rows: how many reviews were taken for the property. |
review_id | string / null | Trip.com's review id (stable; use it to dedupe scheduled runs). |
rating | number / null | Overall score on Trip.com's 0-10 scale (hotel rows: the property's overall score). |
rating_5 | number / null | The same score on the 5-star scale. |
rating_text | string / null | Trip.com's word for the score: Outstanding, Amazing, Great, Very good, Good… |
rating_location | number / null | Location sub-score (0-10). |
rating_facility | number / null | Amenities sub-score (0-10). |
rating_service | number / null | Service sub-score (0-10). |
rating_room | number / null | Cleanliness sub-score (0-10). |
text | string / null | The review, in the language it was written in. |
language | string / null | Language code of the review text (en, zh, ja, fr…). |
recommend | boolean / null | Whether the guest recommends the hotel. |
review_date | string / null | When the review was posted (ISO 8601). |
check_in | string / null | Check-in date of the stay (YYYY-MM-DD). |
room_type | string / null | Room type booked. |
room_id | string / null | Trip.com's room type id. |
travel_type | string / null | Couple, Family, Business traveler, Solo traveler, Traveling with friends, Booked for others, Other. |
travel_type_id | integer / null | Trip.com's id for the travel type. |
reviewer_name | string / null | Reviewer's display name. |
reviewer_country | string / null | Reviewer's country or region. |
reviewer_country_code | string / null | ISO country code of the reviewer. |
reviewer_reviews | integer / null | How many reviews the reviewer has written on Trip.com. |
reviewer_level | string / null | Trip.com reviewer grade (Rising review star, Review Specialist…). |
helpful_votes | integer / null | Helpful votes the review received. |
images | array / null | Photo URLs attached to the review. |
source | string / null | Where the review came from: Trip.com, ctrip, Expedia Group verified review, Hotels.com verified review. |
source_code | integer / null | Trip.com's numeric source code. |
response | string / null | The hotel's public reply, when it replied. |
response_date | string / null | When the hotel replied. |
target | string / null | Status rows: the input this row is about. |
status | string / null | Status rows: ok, no_reviews or error. |
reviews | integer / null | Status rows: review rows delivered for the property. |
filtered | integer / null | Status rows: reviews dropped by maxRating / requireText (never charged). |
pages | integer / null | Status rows: review pages read. |
total | integer / null | Status rows: how many reviews Trip.com shows for the property. |
duplicates | integer / null | Status rows: 1 when this input pointed at a property already harvested in the run. |
error | string / null | Status rows: why the property failed, if it did. |
fetched_at | string / null | When the row was fetched (UTC, ISO 8601). |
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.0.9; it is not a promise that the source has matching rows today.
{
"actor": "kestrel/trip-com-reviews-scraper",
"input": {
"startUrls": [
"https://www.trip.com/hotels/lisbon-hotel-detail-2561632/valverde-hotel/"
],
"maxReviewsPerHotel": 3,
"reviewsSort": "most_recent"
},
"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.
| Event | USD each | What is charged |
|---|---|---|
review | $0.004 | One guest review of a Trip.com or Ctrip hotel: 0-10 rating (and out of 5) with four sub-scores, rating word, review text as written, language, recommend flag, review and check-in dates, room, travel type, reviewer name, country, level and review count, helpful votes, photos, source (Trip.com, Ctrip, Expedia, Hotels.com) and the hotel's reply with date (row keys rating, rating_5, rating_location, rating_facility, rating_service, rating_room, rating_text, text, language, recommend, review_date, check_in, room_type, travel_type, reviewer_name, reviewer_country, reviewer_level, reviewer_reviews, helpful_votes, images, source, response, response_date): $4 per 1,000 reviews. Not charged: hotel rows, status rows, reviews removed by maxRating or requireText, reviews Trip.com's language filter skips (never fetched), a hotel given twice (URL and id of one hotel are read once), hotels with no reviews, unknown ids, bad input. No start fee; proxy and compute are included in the event price. Trip.com pages 100 reviews at a time. The run stops at the maximum cost per run you set when starting it (Apify run option maxTotalChargeUsd), never above it. |
Contracts for agents
- Input schema and sample input
- Prepared MCP call and pricing events
- Full Actor instructions and limits
- REST API
Public contract checked 2026-11-11. Active build: 1.0.9. Refresh live details before a large or recurring run.