ThomasCook

Get list of available destination countries for holidays search. Returns country names and two-letter codes.

Get available regions and cities for a specific destination country. Returns region/city names and codes usable with the search_packages regionCode parameter to narrow holiday search results.

Search for travel destination ideas using a natural language query. Returns curated destinations with pricing (per person), reasons why they fit the user's preferences, and identifiers for downstream package searches. Use this as the entry point for destination DISCOVERY queries ("somewhere warm", "beach vacation", "exotic in March", "family trip to Mediterranean"). TWO INPUT CHANNELS — split user intent from booking context: `query` carries ONLY the user's intent for THIS turn (what they just said, lightly normalized). Keep it short. Do NOT stuff the full conversation history here. `context` carries the FULL, CURRENT, ACCUMULATED state of every constraint the user has stated at ANY point in the conversation. On EVERY call send the complete current context, not just the delta. When the user mutates a value (new budget, new dates, new origin), REPLACE the old value and keep everything else intact. Fields to enumerate in `context` (include every one the user stated): - origins: departure airport(s) or city name(s) (IATA if known: WRO, KRK, LHR) - destination / region / country + explicit exclusions - travel dates + flexibility - passenger composition: adults count, children count, and EACH child's age ("4 adults + 2 children aged 1 and 4", never just "4 adults + 2 children") - budget: amount + currency + per-person vs. total - hotel: star rating, board type (all-inclusive, HB, BB...), amenities - flight preferences: direct-only, duration cap, airline - running exclusions: "do not return: [Rome, Malta, Barcelona]" QUERY BUILDING RULES: - Do NOT enrich with keywords the user never mentioned (no assumed interests, tags, or defaults) - Do NOT add "2 adults" or "departure from Poland" unless the user explicitly stated it - When refining ("cheaper", "more exotic", "farther"), keep query = original + refinement word, and add "do not return: [previously shown destinations]" to context SMART DATE WINDOW — for long weekends / bank holidays, expand ±1–2 days for flight flexibility: - "majówka 2027" (1–3 May) → dates: 2027-04-30..2027-05-04 - "May bank holiday 2027" (Mon 3 May) → dates: 2027-04-30..2027-05-04 Examples of the query/context split: Turn 1: user asks for "family beach holiday in Mediterranean, 4 adults + 2 children aged 1 and 4, 15–22 July 2026, from Wrocław, budget 20000 PLN total, all-inclusive hotel with pool" → query: "family holiday Mediterranean beach" → context: "origins: WRO; dates: 2026-07-15..2026-07-22 (fixed); pax: 4 adults + 2 children aged 1 and 4; budget: 20000 PLN total; hotel: all-inclusive, pool" Turn 2: user says "cheaper" → query: "family holiday Mediterranean beach cheaper" → context: "origins: WRO; dates: 2026-07-15..2026-07-22 (fixed); pax: 4 adults + 2 children aged 1 and 4; budget: 20000 PLN total; hotel: all-inclusive, pool; do not return: [Rome, Malta, Barcelona]" GUARDRAILS: - Do NOT invent destinations — only return results from this tool - If the tool returns an empty list, retry ONCE with a shorter, broader query (remove constraints, do not add new ones). If still empty, inform the user and ask them to rephrase. - locationId and arrivalAirportCode are opaque identifiers — pass them verbatim to downstream package search tools; never modify or invent values. - After presenting results, wait for the user to choose a destination before calling search_packages.

Search for holidays / vacation packages (flights + hotel) to a specific destination country. Returns packages with hotel details, flight info, pricing, and booking links. Only countryCode is required; other parameters are optional with sensible defaults (dates: next 2 months, nights: 7, adults: 2). Supports filtering by price range, hotel stars, meal plan, region, departure airport, and sorting by price, rating, stars, or popularity. Use regionCode from get_regions for region-specific searches. Supports pagination via cursor.