MolTravel

Look up an airline by IATA (2-char) or ICAO (3-char) code.

Search airlines by name. Returns up to 20 results.

Look up an airport by IATA (3-char) or ICAO (4-char) code. Returns full details including runways.

Find airports near a geographic point. Returns results sorted by distance.

Search airports by name or city. Returns up to 20 results sorted by size.

Check which static datasets (airports, airlines, visas) are loaded and their row counts.

[fcdo] List all countries with UK FCDO travel advice.

[fcdo] Get UK FCDO travel advice for a specific country. Includes safety, entry requirements, health, and warnings.

[ferryhopper] Find all direct ferry routes and reachable destination ports from a given origin port without layovers or transfers.

[ferryhopper] Find all ferry travel disruptions, including delays, weather alerts, and strikes for a given date and country.

[ferryhopper] Find ferry ports, harbors, maritime terminals, port IDs, codes, and geographic locations.

[ferryhopper] Search ferry trips as an ordered chain of 1 to 5 legs. Takes human-readable location names (e.g. city or port name) for each leg, not port codes — no need to call get_ports first. Availability flags (cabin, vehicles, pets, e-ticket) are reported per segment. - One leg: a plain one-way search. - Two legs where leg 2 reverses leg 1 (e.g. leg 1 Piraeus→Mykonos, leg 2 Mykonos→Piraeus): a round trip. - Up to 5 legs otherwise (e.g. A to B, then B to C, then C to D): an island-hopping chain. Legs after the first must depart from the location the previous leg arrived at, and must be in chronological order (a later leg may share the same date as an earlier one, but may not precede it). The response returns each leg's available options independently (legs[].options) — options are never filtered against another leg's options. Consecutive legs must leave enough time between one leg's arrival and the next leg's departure to be a valid connection; this is not pre-filtered server-side or reflected in this output, so do not assume every combination of options across legs is a valid connection — the widget the user interacts with enforces this.

[ferryhopper] Deprecated: prefer search_ferry_trips, which covers this tool plus round-trip and multi-leg search and per-segment availability flags. Get a list of available one-way ferry trips between two ports on a specific date.

[ferryhopper] Get full details for a single sailing leg, looked up by the id of one of the options returned by search_ferry_trips (legs[].options[].id). Returns the trip's departure/arrival time, ports, and operating company, plus the vessel's technical specs, onboard amenities, and photos. Use this to answer questions about a vessel such as: does it have wifi / a restaurant / a snack bar / an open deck / a lift or elevator / wheelchair or disabled access / a designated smoking area? Is it pet-friendly, or does it allow pets on board? Does it have cabins, or a garage / vehicle deck for cars and motorbikes? How many passengers or vehicles does it carry (capacity)? How long is the vessel (length in meters)? What is its IMO number or MMSI (maritime identification numbers used for registry/tracking lookups)? Is this vessel accessible, family-friendly, or suitable for passengers who need mobility assistance? What does the vessel look like (photos)? If no detailed specs exist for the vessel in the source system, vessel.hasDetails is returned as false and every spec/amenity field is null — this means the data is unavailable, not that the vessel lacks that amenity. Also returns the trip's bookable accommodation tiers (seat/cabin classes) with their price and a photo of that accommodation, when available. Throws if the tripId is malformed or the trip is no longer bookable (e.g. it has already departed, was cancelled, or sold out) — re-run search_ferry_trips to get a fresh tripId in that case.

[peek] Get availability information for a specific experience including dates, times, and pricing

[peek] Get detailed information about a specific experience by ID

[peek] List all category tags

[peek] Render activity tiles for a list of activity IDs, returning an embeddable widget URI

[peek] Search for travel experiences with comprehensive filtering options. Returns available categories, tags, and regions with IDs for further filtering.

[peek] Search for regions by name

[restcountries] Look up country information from REST Countries.

[skiplagged] Search Skiplagged for rental cars between pickup and dropoff locations/dates, returning prices, companies, and car details.

[skiplagged] Find lower-priced destinations from a departure city when the user is flexible about where to go.

[skiplagged] Search Skiplagged support articles for answers about its services, products, and policies.

[skiplagged] Generate a flexible calendar of the lowest one-way fares around a chosen departure, returning date → cheapest-price entries to help pick the best day to fly. Intended for flexible-date price discovery, not exact itinerary selection.

[skiplagged] Generate a flexible round-trip price calendar for a fixed-length stay around a chosen travel window. Returns (depart date, return date, lowest total price) entries for nearby date pairs that preserve the original trip length; intended for price discovery, not exact itinerary selection.

[skiplagged] Search Skiplagged for flights between specific locations with filtering options for passengers, fare class, stops, airlines, and timing preferences

[skiplagged] Fetch room-level availability, pricing, and amenities for a specific hotel and stay dates.

[skiplagged] Search Skiplagged for hotels in a city with specific check-in and check-out dates, including ratings and pricing.

[skiplagged] Resolve a city name to a valid IATA code

[skiplagged] Resolve coarse location metadata supplied by the client to the nearest airport. Takes no user-provided arguments.

[tourradar] Use this when you need to find a tour operator's ID by their name for filtering tours. Searches tour operators by name and returns matching operators with their IDs. Use the returned operator ID with tour search filters.

[tourradar] Use this when you need to find city IDs for tour search filters like start city, end city, or cities to visit. Searches for cities by name within a specific country. Supports multiple name variants to handle different spellings (e.g., Krakow, Kraków, Cracow).

[tourradar] Use this when you need continent IDs for filtering tours by region. Returns a list of all supported continents with their IDs and names for use in tour search filters.

[tourradar] Use this when you need to look up country IDs for filtering tours or validating country names. Returns a complete list of all supported countries with their IDs, names, and ISO country codes.

[tourradar] Use this when you need to check supported currencies or get currency details like symbols. Returns a list of all supported currencies with their codes (USD, EUR), names, and symbols ($, €).

[tourradar] Use this when you need language IDs for filtering tours by guide language. Returns a list of all supported languages with their IDs, codes, and names for use in tour search filters.

[tourradar] Use this when the user wants information about a tour operator, such as their terms and policies. Fetches operator details including name, code, and terms & conditions based on operator ID.

[tourradar] Use this when the user asks about available departure dates, pricing for specific dates, or needs to validate if a departure date is available. Returns a list of departures for a specific tour within a date range, including availability status, pricing, and booking information.

[tourradar] Use this when the user wants to see detailed information about a specific tour. Fetches comprehensive tour details including itinerary, pricing, operator info, images, and booking links based on tour ID.

[tourradar] Use this when the user has questions about a tour that might be answered in the FAQ section. Returns a paginated list of frequently asked questions and answers about a specific tour, covering topics like inclusions, requirements, and policies.

[tourradar] Use this when the user wants to see tour routes on a map or compare itineraries visually. Fetches tour details for one or more tours and prepares map data with all itinerary locations, coordinates, and day-by-day information for visual display.

[tourradar] Use this when you need tour type IDs for filtering tours by category like adventure, cultural, or wildlife. Returns a hierarchical list of tour type groups and their individual types with IDs and names.

[tourradar] Use this when you need to know the current date, especially before setting departure date filters. Returns the current date and time in ISO format. Essential for calculating valid date ranges for tour searches.

[tourradar] Search tour reviews using AI-powered semantic search. Requires tourIds to scope results to specific tours. Use this when the user asks about reviews, feedback, or experiences for specific tours. Combine with an optional text query to find reviews mentioning specific topics (e.g., 'food', 'guide', 'accommodation'). When you don't have tour IDs, use vertex-tour-search or vertex-tour-title-search first to find them.

[tourradar] Use this when the user describes what they want in natural language and you need AI-powered semantic search to understand their intent. Before use this tool, please READ all possible filters. PLESE USE FILTERS, when can be used, to make search faster and much more precise. Please use start_city, end_city, cities, countries, start_country, end_country filters if possible. You can use multiple of them. AI-powered semantic search for tours using natural language queries combined with optional filters. Uses Google Vertex AI to understand intent and find relevant tours based on descriptions, themes, or specific requests. Use `vertex-tour-search` when: - The user describes what they want in natural language - You need semantic/AI-powered search to understand intent - Combining natural language with filters for refined results Examples: - "Family-friendly safari with kids under 12" - "Romantic honeymoon trip with beach and mountains" - "Adventure tour with hiking and camping for beginners" - "Cultural immersion experience with local homestays" - "Wine tasting tour through European countryside" ## Input ### Required - `textSearch`: Natural language description of what the user is looking for - `display_mode`: How to display results — `"listing"` (default, carousel of tour cards) or `"map"` (interactive map view) ### Optional Filters #### Location Filters | Filter | Type | Description | | --------------- | -------- | -------------------------------------------------------------------------- | | `start_country` | string[] | Country where tour BEGINS (ISO 3166-1 alpha-2 codes). OR logic. | | `end_country` | string[] | Country where tour ENDS (ISO 3166-1 alpha-2 codes). OR logic. | | `start_city` | number[] | City IDs where tour starts. Use `b2b-cities-search` to find IDs. OR logic. | | `end_city` | number[] | City IDs where tour ends. Use `b2b-cities-search` to find IDs. OR logic. | | `countries` | object | Countries visited DURING the itinerary. Supports AND/OR operator. | | `cities` | object | Cities visited on the itinerary. Supports AND/OR operator. | #### Range Filters | Filter | Type | Description | | ---------------- | ------------------------ | ------------------------------------------------------------------------------------ | | `duration` | `{ min, max }` | Tour length in days | | `max_group_size` | `{ min, max }` | Maximum group size range | | `min_group_size` | `{ min, max }` | Minimum group size range | | `min_age` | `{ min, max }` | Minimum age requirement range. E.g., `{ min: 1, max: 12 }` finds family-friendly tours | | `max_age` | `{ min, max }` | Maximum age limit range. E.g., `{ min: 18, max: 39 }` finds youth-specific tours | | `price` | `{ min, max, currency }` | Price range (currency: "EUR") | #### AND/OR Filters These filters support both AND and OR operators: | Filter | Values | Description | | ------------ | ------------------------ | ---------------------------------- | | `departures` | YYYY-MM strings | Filter by departure months | | `countries` | ISO 3166-1 alpha-2 codes | Countries visited during itinerary | | `cities` | City IDs | Cities visited on itinerary | Structure: `{ values: [...], operator: "AND" | "OR" }` - `OR` (default): Tour matches ANY of the specified values - `AND`: Tour must match ALL specified values ## Examples ### Simple text search ```json { "textSearch": "family adventure with wildlife" } ``` ### With location filters ```json { "textSearch": "hiking adventure", "start_country": ["DE", "AT"], "countries": { "values": ["IT", "CH"], "operator": "AND" } } ``` ### With range filters ```json { "textSearch": "luxury beach vacation", "duration": { "min": 7, "max": 14 }, "price": { "min": 2000, "max": 5000, "currency": "EUR" }, "max_group_size": { "min": 1, "max": 16 } } ``` ### With age filters ```json { "textSearch": "family safari with young children", "min_age": { "min": 1, "max": 6 }, "duration": { "min": 7, "max": 14 } } ``` ### With departure dates ```json { "textSearch": "northern lights tour", "departures": { "values": ["2026-01", "2026-02", "2026-03"], "operator": "OR" } } ``` ### Map display mode ```json { "textSearch": "hiking tours in the Alps", "display_mode": "map", "countries": { "values": ["AT", "CH"], "operator": "OR" } } ``` ## Response Returns a list of tours matching the query, each containing: - Tour ID, name, and URL - Operator information - Brief description matching the query context

[tourradar] Search for tours by title using AI-powered semantic search. Returns a list of matching tour IDs and titles. Use this when you need to look up a tour by name. When you know tour id, use b2b-tour-details tool to display details about specific tour

[tourradar] Use this when the user wants to ASK A QUESTION about a tour or operator WITHOUT committing to a booking. Two modes: - mode "tour": a question about a specific tour. Requires `tourId`. The `departureDate` is OPTIONAL here — if the customer has not picked a date, omit it and the backend will pick the nearest real departure. Do NOT fabricate a date. - mode "operator": a general/operator-level question. Requires `operatorId` and no tour. Always provide the customer's real contact details (email, first/last name; phone optional) and their actual question text. Never fabricate or assume user data — ask for missing information.

[tourradar] Use this when the user explicitly wants to book a tour and has provided their contact details. Creates a booking request for a specific tour. Requires real contact details (email, names; phone optional). Always confirm the departure date by checking departures first. Never fabricate or assume user data - always ask for missing information.

[tourradar] Use this when the user requests a tour brochure or PDF to be sent to their email. Sends a tour brochure (PDF file) to the specified email address. Before using this, ensure the user has provided their email address. If not provided, ask the user for it. Never generate or assume email addresses.