ClaudeListedTier: partner
Tripadvisor
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.
First seen 2 Oct 2026. Evidence as of 2 Oct 2026.
3
Tools
From an anonymous probe
3
Source listings
Each with its own history
0
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| compare_hotels | 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" | Read-only |
| hotel_details | 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. | Read-only |
| search_hotels | 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. | Read-only |
Change history
No changes since the first observation. The first snapshot is the baseline.
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Claude directory (Anthropic subregistry) | 1ddc28c1-c1f8-4894-9a85-f6dc8add9c89 | 2 Oct 2026 | 2 Oct 2026 | 1 |
| claude.com listing page | 1ddc28c1-c1f8-4894-9a85-f6dc8add9c89 | 2 Oct 2026 | 2 Oct 2026 | 1 |
| MCPTop directory snapshot | anthropic:1ddc28c1-c1f8-4894-9a85-f6dc8add9c89 | 2 Oct 2026 | 2 Oct 2026 | 1 |