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 ContextMint Bridge (your signed-in browser tab) 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 'this browser can't serve a capability' 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 distinct operations (search by name, search nearby, photos, reviews, batch details). The main overlap is between ta_web_get_location and ta_get_location_details, which both retrieve location details; the description clarifies one is a fallback, but an agent could still misselect if not reading carefully.
All names use snake_case with a consistent ta_ prefix. Most follow verb_noun (get, search), but ta_web_healthcheck is a noun and the ta_web_* vs ta_* split creates a minor stylistic variation.
Eight tools is well-scoped for a read-only TripAdvisor client. Each tool covers a distinct capability (search, nearby, details, photos, reviews, batch, fallback, diagnostics) without obvious redundancy.
The surface covers the full read lifecycle for TripAdvisor locations: discovery (search/nearby), detail retrieval (single and batch), sub-resources (photos, reviews), and a fallback path for API key issues. No obvious missing operations for a public-data client.