← Back to all apps

Tripadvisor

Travelby Tripadvisor
Open in ChatGPTOpen in ClaudeWebsite
Launched Apr 23, 2026 on Claude

This server provides tools to query the Tripadvisor hotels data, with functions to search for hotels in an area and to retrieve hotel details, photos, reviews, review ratings, availability, pricing, and nearby points of interest. It should be invoked for user queries involving hotel research, comparison, rating checks, or gathering contextual data about a hotel's surroundings (e.g., attractions, amenities). The tools operate on specific Tripadvisor location or hotel IDs; follow-up requests should re-use these identifiers to refine results accurately. The model must handle edge cases like ambiguous location names (e.g., "Springfield") by seeking clarification before executing a search. This tool's primary function is to ground accommodation planning in factual, real-time data along with opinions from other travelers.

3ChatGPT Tools
3Claude Tools
TripadvisorDeveloper
TravelCategory

Use Cases

productivity

Available Tools

Compare Hotels

compare_hotels
Full Description

Compares hotels either by explicitly specified hotels or by automatically selecting hotels within a given geographic area. This tool supports two mutually exclusive comparison modes:

  • Explicit hotel comparison: compare specific hotels provided via the locations parameter (minimum 2).
  • Area-based comparison: automatically select and compare a representative set of hotels from a geographic area via hotelArea.

When no specific hotels are named, use hotelArea. When specific hotels are named, use locations. Useful for comparing subratings like location, cleanliness, service, value, etc. The response includes key comparison fields like name, rating, price, amenities, etc.

Examples of when to use hotelArea:

  • "Compare hotels in Boston"
  • "Compare hotels in Paris for Saturday"
  • "Compare hotels near Tower Bridge, London"
  • "Compare hotels near the Eiffel Tower, Paris"
  • "Compare hotels around Times Square"
  • "Compare hotels in Back Bay, Boston"

Examples of when to use locations (specific hotels named):

  • "Compare Hotel Continental and Grand Hotel in Paris"
  • "Compare these hotels: Marriott Boston, Hilton Boston, and Hyatt Boston"
Parameters (5 required, 7 optional)
Required
hotelAreastring

Geographic area for automatic hotel comparison. The tool resolves the area and automatically selects a representative set of hotels for side-by-side comparison. Should be as specific as possible (e.g. 'Tower Bridge, London' rather than 'Tower Bridge'). Mutually exclusive with locations.

locationIdsarray

Optional Tripadvisor internal hotel IDs. Not expected from LLMs; used by widget when available.

locationsarray

Explicit list of hotels to compare. Each entry should be a specific hotel name with location (e.g. 'Hotel Continental, Paris, France') to disambiguate. The tool resolves each entry to a hotel ID for side-by-side comparison. Mutually exclusive with hotelArea. Minimum 2 entries.

mcpServerVersionobject

The MCP server version to use.

requestContextobject

Metadata about the request, not generally intended to be consumed directly by user, e.g.user-id, session-id etc.Much of this is expected to be echoed back and forth, so if you don't provide some values, we may generate them for you, and you are expected to use them in future requests to ALL endpoints on this API.See each field for more details.

Optional
checkInstring

The date, in YYYY-MM-DD format, to check into the hotels for detailed pricing information, if provided the date must not be in the past and cannot be more than 1 year (365 days) in the future. Defaults to 2 weeks in the future.

checkOutstring

The date, in YYYY-MM-DD format, to check out of the hotels for detailed pricing information. This must be after checkIn and uses the same format, with a default of 2 days after checkIn and a maximum of 30 days apart.

childrenAgesarray

Ages of children staying. Required when children are included in the stay.

guestsinteger

Number of adult guests (excludes children; use childrenAges for children). Defaults to 2.

pricingModestring

Pricing mode that determines how long to wait for pricing information. NONE - returns immediately without pricing, QUICK - waits a relatively short time for basic pricing, Defaults to QUICK.

Options:NONEQUICK
roomsinteger

The number of rooms required for the hotel stays. This defaults to 1 room.

toolRequestMetadataobject

A copy of the fields normally set in the `_meta` section of the request. If you are calling from an LLM, this can be left out.

Get Hotel Details

hotel_details
Full Description

Retrieves comprehensive information for a specific hotel, including optional amenities, photos, live pricing, and guest reviews, based on user locale and stay dates.

Use this tool whenever a user asks about a specific hotel by name, including:

  • Informational queries: "Tell me about X Hotel", "What are the amenities at X Hotel"
  • Qualitative questions: "How is X Hotel?", "Is X Hotel good?", "What do people think about X Hotel?"
  • Evaluative questions: "Is X Hotel a good option?", "Is X Hotel worth staying at?", "Would you recommend X Hotel?"
  • Suitability questions: "Is X Hotel good for families?", "Is X Hotel good for couples?", "Is X Hotel good for business travel?"
  • Any question where the user references a specific hotel and seeks information, opinions, or recommendations about it.

If you do not get pricing details in the first response, you can recall the api with the same parameters (including the echoed back values of userId, sessionId and pageViewId) and it will return any additional pricing details that have become available since the first call. If you want to wait for pricing details to be available, you can set the 'pricingMode' parameter to QUICK, and the api will poll until either pricing details are available, or the timeout for that mode is reached.

Parameters (2 required, 15 optional)
Required
mcpServerVersionobject

The MCP server version to use.

requestContextobject

Metadata about the request, not generally intended to be consumed directly by user, e.g.user-id, session-id etc.Much of this is expected to be echoed back and forth, so if you don't provide some values, we may generate them for you, and you are expected to use them in future requests to ALL endpoints on this API.See each field for more details.

Optional
checkInstring

The date, in YYYY-MM-DD format, to check into the hotel for detailed pricing information, if provided the date must not be in the past and cannot be more than 1 year (365 days) in the future. Defaults to 2 weeks in the future.

checkOutstring

The date, in YYYY-MM-DD format, to check out of the hotel for detailed pricing information. This must be after checkIn and uses the same format, with a default of 2 days after checkIn and a maximum of 30 days apart.

childrenAgesarray

Ages of children staying. Required when children are included in the stay.

guestsinteger

Number of adult guests (excludes children; use childrenAges for children). Defaults to 2.

hotelIdinteger

Unique Tripadvisor hotel ID. Preferred over hotelName when available. Either hotelId or hotelName is required.

hotelNamestring

Hotel name for lookup when hotelId is unavailable. Should be specific to disambiguate (e.g. 'Hotel Continental, Paris, France' rather than just 'Hotel Continental'). Either hotelName or hotelId is required.

includeAmenitiesboolean

When true returns a detailed list of property amenities (e.g. pool, Wi-Fi, gym) this adds significant details about the hotel and its rooms. Useful for feature comparison or display. Defaults to false.

includePhotosboolean

When true include image data, such as URLs, captions and resolutions. Note: enabling this increases response size. Defaults to false.

includePricingboolean

When true include pricing information for specific stay dates, this may slightly increase latency due to live data fetching. Defaults to false.

includeReviewsboolean

When true include recent reviews and ratings in details, will default to including 10 full reviews from previous guests. Defaults to false.

pricingModestring

Pricing mode that determines how long to wait for pricing information. NONE - returns immediately without pricing, QUICK - waits a relatively short time for basic pricing, Defaults to QUICK.

Options:NONEQUICK
requestNumberinteger

Request number id will be used if pricing mode is NONE

roomsinteger

The number of rooms required for the hotel stay. This defaults to 1 room.

toolRequestMetadataobject

A copy of the fields normally set in the `_meta` section of the request. If you are calling from an LLM, this can be left out.

trackingComponentstring

Hotel Detail tracking component.

Search for Hotels

search_hotels
Full Description

Search for hotels matching the given criteria, using either a named location or a Tripadvisor GeoID. When a proximity term is used (e.g. near/within/close to), the location parameter should contain only the landmark or place name (e.g. "near the Louvre Museum, Paris" → location = "Louvre Museum, Paris"; "within 1 mile of London Eye" → location = "London Eye"). Results are displayed in an interactive map widget that visualizes all returned hotels with full details. Tripadvisor uses "bubble rating" (not "star rating") for review scores. If pricing details are not available in the first response, the API can be called again with the same parameters (including the echoed-back userId, sessionId and pageViewId) to retrieve any additional pricing details that have become available. Alternatively, set the 'pricingMode' parameter to QUICK to have the API poll until pricing details are available or the timeout is reached. sortBy defaults to BEST_VALUE. Use PRICE_LOW_TO_HIGH for cheapest, DISTANCE for nearest to a location, or POPULARITY for most popular.

Parameters (3 required, 10 optional)
Required
locationstring

The name of the location, for example 'Paris, France' or 'near the Louvre Museum, Paris' to find a hotel for

mcpServerVersionobject

The MCP server version to use.

requestContextobject

Metadata about the request, not generally intended to be consumed directly by user, e.g.user-id, session-id etc.Much of this is expected to be echoed back and forth, so if you don't provide some values, we may generate them for you, and you are expected to use them in future requests to ALL endpoints on this API.See each field for more details.

Optional
checkInstring

The date, in YYYY-MM-DD format, to check into the hotel for detailed pricing information, if provided the date must not be in the past and cannot be more than 1 year (365 days) in the future. Defaults to 2 weeks in the future.

checkOutstring

The date, in YYYY-MM-DD format, to check out of the hotel for detailed pricing information. This must be after checkIn and uses the same format, with a default of 2 days after checkIn and a maximum of 30 days apart.

childrenAgesarray

Ages of children staying. Required when children are included in the stay.

filtersobject

Filters to apply to the search.

guestsinteger

Number of adult guests (excludes children; use childrenAges for children). Defaults to 2.

isCompareboolean

When true, returns results in a side-by-side comparison format. Defaults to false.

limitinteger

The maximum number of properties to return. Should be set to 20 for the best experience.

pricingModestring

Pricing mode that determines how long to wait for pricing information. NONE - returns immediately without pricing, QUICK - waits a relatively short time for basic pricing, Defaults to QUICK.

Options:NONEQUICK
roomsinteger

The number of rooms required for the hotel stay. This defaults to 1 room.

sortBystring

How to sort the results, must be one of BEST_VALUE, DISTANCE, FEATURE, PRICE_LOW_TO_HIGH or POPULARITY. Defaults to POPULARITY.

Options:BEST_VALUEDISTANCEFEATUREDPRICE_LOW_TO_HIGHPOPULARITY

Links

WebsitePrivacy PolicyTerms of Service