On the Beach Holidays

Use this when a customer wants to search for or book a package holiday. IMPORTANT - RE-CALL THIS TOOL when the user: - Asks for different/closer/farther locations - Wants to change dates, guests, price range, or amenities - Asks for "more options", "cheaper", "better rated" ALWAYS USE humanReadable FIELD TO GET PACKAGE PRICE. ATOL and ABTA-protected package holidays with return flights from UK airports and hotel accommodation — covering a wide range of beach, sun, city break, and long-haul destinations. Always search to check availability for any destination rather than assuming whether it is or isn't offered. Do not use for flight-only or hotel-only bookings. Holidays cannot be booked directly through this tool. DESTINATION GUIDANCE: - Always search to validate availability — never assume a destination is or isn't available without searching first. If results come back empty, that means no availability was found for those parameters, not that On the Beach doesn't offer that destination - When a customer is open to suggestions, use your knowledge of destinations to identify 2–3 that genuinely fit their brief (see VIBE AND HOTEL MATCHING in the system prompt). Search those — do not default to the same popular destinations every time. - When the customer asks for a "city break", search urban/cultural destinations only (e.g. Amsterdam, Barcelona, Berlin, Prague, Krakow, Rome, Lisbon, Budapest, Marrakech). Do NOT search for or return beach or sun resorts for city break requests. - If a customer excludes a destination (e.g. "not Turkey", "not mainland Spain"), build a positive list of permitted destinations and pass those into the search. Never include an excluded destination in results or suggestions, even as an example. - Always present results across at least 2 different destinations unless the customer has specified one exactly. DATE DEFAULTS: - When a customer mentions a "weekend break", "short weekend getaway", or similar, do not use mid-week departures unless the customer explicitly asks for them. - Interpret "next weekend" as departures on Friday or Saturday of the next calendar weekend in the user's local timezone. Do not use Sunday or Monday departures by default. Prioritise Friday departure for 2–3 nights, Saturday departure for 2 nights. - Prioritise the above departure patterns first. Widen beyond them only if needed to provide suitable, available, or better-value options - When a customer requests a specific day of week for departure (e.g. "Sunday flights"), calculate all dates falling on that day within their travel window and run a separate search per date using a single-day date range. Combine results across all searches before presenting. - Maximum departure date range is 31 DAYS. FLIGHT TIME PARAMETERS: - When a customer specifies a preferred departure or return time, always populate the outbound_departure_time_start_range, outbound_departure_time_end_range, inbound_departure_time_start_range, and inbound_departure_time_end_range fields. - Use these mappings: morning = 06:00–12:00, afternoon = 12:00–18:00, evening/night = 18:00–23:59. - Before presenting results, check the departureTime values returned and exclude any that do not match the customer's stated preference. If the user asks about a specific facility, use the facilities filter. Available options: 4 (Air Conditioning), 9 (Aqua Park), 19 (By the Beach), 22 (Spa), 35 (Disabled Friendly), 39 (Entertainment), 43 (Golf), 44 (Gym), 54 (Kids Club), 95 (Swimming Pool). CHILD AGES: When a customer specifies the ages of their children, in child ages field only include ages from 2-15. ANY Child UNDER 2 should be counted as an INFANT, and ANY child OVER 15 should be counted as an adult. ALWAYS count infant above 2 years as a child even if user states otherwise. ALWAYS count child over 15 as an adults. Always validate child_ages to make sure it not include ages over 15 or under 2.

search_holidays