tripadvisor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRIPADVISOR_API_KEY | Yes | Content API key, sent as the `key` query parameter. | |
| TRIPADVISOR_REFERER | No | Referer header for domain-restricted keys (the API 403s without a matching referer). | |
| TRIPADVISOR_CACHE_TTL | No | Seconds to cache search responses (default: 300; `0` disables). | |
| TRIPADVISOR_STATIC_CACHE_TTL | No | Seconds to cache details/photos/reviews (default: 3600; `0` disables). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ta_search_locationsA | Search TripAdvisor locations (restaurants, attractions, hotels) by name. Returns matches with a location id for the detail tools, plus pagination. Returns slim summaries by default; pass view:"full" for the whole records. |
| ta_search_nearbyA | Find TripAdvisor locations near a point within a radius, or inside a bounding box. Center by lat+lon+radius, by a reference location_id+radius, or by a sw/ne bounding box. Returns matches with distance and a location id. Returns slim summaries by default; pass view:"full" for the whole records. |
| ta_get_locationsA | Get details for MULTIPLE locations in one call (batch). Pass an array of location ids — cheaper than repeated ta_get_location_details. Unknown or unlicensed ids are silently omitted. Returns slim summaries by default; pass view:"full" for the whole records. |
| ta_get_location_detailsA | Get full details for a TripAdvisor location: names, descriptions, address, coordinates, traveler ratings, phone, category, and listing URLs. Rating-icon and other incidental image URLs are dropped by default; pass view:"full" for TripAdvisor's whole record. |
| ta_get_location_photosA | Get photos for a TripAdvisor location (multi-size image URLs, source, dimensions), with pagination. |
| ta_get_location_reviewsA | Get traveler reviews for a TripAdvisor location, with pagination. Reviewer avatars and other image URLs are dropped by default; pass view:"full" for TripAdvisor's whole records. |
| ta_web_healthcheckA | Round-trips a small public www.tripadvisor.com URL (/) through the fetchproxy bridge and returns diagnostics: the bridge's role (host/peer/null), port, version, the extension link (linked / pair pending / not attached / never answered), the elapsed round-trip time, and a plain-English hint distinguishing 'bridge never came up' from 'extension not connected' from 'real www.tripadvisor.com-side problem'. Read-only, no auth required. Call this when a real tool fails and you want to know which hop broke. |
| ta_web_get_locationA | Get a TripAdvisor location's core details (name, rating, review count, address, coordinates, phone, photo, listing URL) by location ID, read from the public page via the browser bridge. Works without an API key — use this when ta_get_location_details is unavailable or its key is blocked. Covers attractions, hotels, and restaurants. Does not return individual review text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools target clear actions (search, nearby, photos, reviews, healthcheck), but there is real overlap among ta_get_locations, ta_get_location_details, and ta_web_get_location—all return location details in slightly different modes. The descriptions do clarify batch vs single vs API-key-free fallback, so an agent can disambiguate if it reads carefully.
The ta_ prefix and get/search verb pattern are consistent overall. Minor deviations include ta_web_healthcheck (a noun instead of verb_noun) and the awkward ta_web_get_location placement, plus plural/singular inconsistencies like ta_get_locations vs ta_get_location_details.
Eight tools is a well-scoped size for a TripAdvisor location server. Each tool covers a distinct retrieval need (search, nearby, details, batch, photos, reviews, diagnostics, web fallback) without bloat.
The read-only domain is fully covered: search by name, proximity search, single and batch details, photos, reviews, and a fallback/diagnostic path. No obvious lifecycle operations are missing because the TripAdvisor domain is inherently read-only.