Booking.com

The ISO 3166-1 alpha-2 country code for the user's location in lowercase. The following country codes are not supported: [ir, ru, by, cu, kp, sy]. Do not call this tool if the user is from one of the non-supported countries.

Use this to classify user accommodation requests into a list of specific accommodation subtypes. Only include specific subtypes explicitly mentioned by the user; otherwise leave this empty.

The guest's arrival date in ISO 8601 format (YYYY-MM-DD). If not provided, you **must** use the next weekend (2 days) as the default

The guest's departure date in ISO 8601 format (YYYY-MM-DD). This must be after the check-in date and within 90 days of check-in. If not provided, you **must** use the next weekend (2 days) as the default

Geographic coordinates for a location-based search. Searching with coordinates is useful when users want to search for accommodations near a landmark. Mutually exclusive with destination - provide either destination OR coordinates, not both.

The ISO 4217 currency code for displaying prices in uppercase. Only fill this field if the user explicitly mentions the desired currency.

Location name for accommodation search, written in English. Only call this tool once with the most relevant destination. Accepts cities, districts, neighborhoods, regions, hotels, airport IATA codes, landmarks, transit stations/stops, and other widely recognized points of interest. CRITICAL REFINEMENT RULE: If the user provides a city/region AND an additional location hint that is vague, abbreviated, or underspecified (e.g., a local name, line/zone label, informal area name, venue/campus reference, or 'near X'), you MUST incorporate that hint by refining the destination to a more specific, canonical place name that a map/search engine would recognize (e.g., a specific neighborhood, station/stop, major venue, or landmark) within the intended city/area. Do not ignore or drop the hint. Prefer the most representative/central matching place for that hint. If multiple interpretations exist and no single canonical place is clearly best, choose the most prominent option rather than leaving the destination broad. Mutually exclusive with coordinates - provide either destination OR coordinates, not both. Use proper spelling with special characters (e.g., "Córdoba" not "Cordoba"). Examples: - City: "Paris" - District/Neighborhood: "Trastevere", "SoHo" - Region: "Tuscany", "Bavaria" - Hotel: "Hilton Paris Opera" - Airport: "JFK" - Landmark/POI: "Eiffel Tower" - Transit stop/station: "Central Station"

Use this to list facility names. Populate ONLY if the user explicitly requests a facility. The search matches ALL facilities listed. Guardrail: Do NOT infer facilities from descriptive words or general requests (e.g., 'family-friendly'). CRITICAL: If the search returns zero results, MUST try the search again with fewer facilities or with this field left empty.

Rules: - Include ONLY on-site amenities or room views (ignore off-site proximity or locations). - If a request is general (e.g., 'pool'), map it to the general enum AND all specific variations (e.g., SWIMMING_POOL, INDOOR_..., OUTDOOR_...). - Exclude features the user explicitly negates. - Order by priority: Primary requests first, then secondary/bonus features. - Ignore features mentioned only by the Assistant. - If no possible themes match the conversation, return an empty array.

Use this when the user mentions a preference on the meals that need to be included at the property stay. Only include the meal plan if explicitly mentioned by the user; otherwise leave this empty. IMPORTANT: Map natural-language meal requests to this field, NOT to facilities. For example, "I want breakfast" → breakfast_included.

The minimum review score of the hotel the user is looking for. Only return a value if the user explicitly mentions the review score level they are looking for. If the user explicitly mentions 'superb/excellent review score', the value should be 9. If the user explicitly mentions 'High/Very good review score', the value should be 8. If the user explicitly mentions 'Good review score', the value should be 7. Else return null, including cases when the user doesn't say anything about review scores.

Total number of guests (adults and children combined) for the entire stay across all rooms.

The total number of separate rooms needed for the stay.

Price per night range for the given search.

Limit search results to accommodations with specific star ratings. Populate ONLY when the user explicitly requests a star rating (e.g., “5-star hotels”, “3 or 4 stars”). Array of integers from 1 to 5. The search matches ANY rating in the array (OR logic). For ranges like “3 stars or higher”, include [3, 4, 5].

A short and concise natural language query in English that strictly and only contains the requirements explicitly mentioned by the user. Hard requirements: Absolutely cannot use any personally identifiable information (like personal names, dates of birth, identification numbers, bank account numbers, etc.). Absolutely must not include specific location details (street names, street numbers, or specific house/apartment names); use only general location identifiers (city, neighborhood, area, or a major landmark). You are not allowed to include default parameters in the query, only use facts the user explicitly mentioned. Be written from the user perspective, matching the user’s style. Include all explicitly stated requirements (e.g., facilities, travel date/period, location) and explicitly stated secondary needs (e.g. romantic / luxurious / maybe a spa). Resolve multi-turn conversation context into a single, complete request. Be descriptive, concise, and specific, but do not add extra constraints or qualifiers the user didn’t explicitly ask for.

The guest's arrival date in ISO 8601 format (YYYY-MM-DD). If not provided, default to the next upcoming Saturday.

The guest's departure date in ISO 8601 format (YYYY-MM-DD). This must be after the check-in date and within 90 days of check-in. If not provided, default to 2 nights after check-in.

The ISO 3166-1 alpha-2 country code for the user's location in lowercase. The following country codes are not supported: [ir, ru, by, cu, kp, sy]. Do not call this tool if the user is from one of the non-supported countries.

Use this to classify user accommodation requests into a list of specific accommodation subtypes. Only include specific subtypes explicitly mentioned by the user; otherwise leave this empty.

Mandatory when the user intends to bring children. The ages of the children. If the user did not provide the ages, you must ask a follow-up question asking the user about the children's ages before calling the tool.

Geographic coordinates for a location-based search. Use this instead of destination when: - The user wants accommodations near a specific non-accommodation place (hospital, office, university, restaurant, venue, gym, etc.) — estimate the latitude and longitude of that place. - The user provides an exact address or a location too specific for a city/neighborhood name. - The user mentions a small, locally-known area within a city (a specific intersection, market, circle, or micro-neighborhood that is unlikely to be recognized by a global search engine) — estimate the coordinates of that area. Mutually exclusive with destination — provide either destination OR coordinates, not both.

The ISO 4217 currency code for displaying prices in uppercase. Only fill this field if the user explicitly mentions the desired currency.

The place name to search for accommodations, in English. Must be a single, specific location — not a sentence, question, or list of places. Supported types: city ("Paris, France"), neighborhood ("Trastevere, Rome"), region ("Tuscany, Italy"), hotel name ("Hilton Paris Opera"), airport IATA code ("JFK"), landmark ("Eiffel Tower, Paris"), transit station ("Central Station, Amsterdam"). Rules: - One location only. Never comma-separate multiple cities or regions. - Include the parent region or country when the name is ambiguous (e.g., "Paris, Texas" not just "Paris", "Cambridge, MA" not just "Cambridge"). - Use the canonical English name with proper diacritics (e.g., "Córdoba, Spain", "Cancún, Mexico"). - If the user mentions a vague area within a city, resolve it to the most specific recognizable place name (e.g., "near the Louvre" → "Louvre, Paris"). - Never include dates, filters, or natural language queries (e.g., "hotels in Paris on June 5" is wrong — just pass "Paris, France"). - If the user mentions a specific place that is NOT an accommodation (not a hotel, hostel, resort, apartment, lodge, B&B, or villa), use coordinates instead of this field. This includes hospitals, restaurants, offices, schools, gyms, shops, and other non-lodging locations. - For small or locally-known sub-areas within a city (e.g., a specific intersection, circle, or micro-neighborhood), prefer coordinates to pinpoint the location. If coordinates are not feasible, use the well-known parent district or city instead (e.g., "Bangalore" instead of "Anand Rao Circle, Bangalore"). - When the user asks for a specific hotel by name, use a short canonical name without branch qualifiers or suffixes (e.g., "Hilton Paris Opera" not "Hilton Paris Opera Hotel & Spa"). - Mutually exclusive with coordinates.

Use this field only for property facilities the user clearly requires to filter results. The search matches ALL listed facilities, so add only clear hard filters. If unsure, leave this field empty. Use ONLY exact facility enum values. Do not repeat image_themes concepts in facilities. If the request is mainly about photos, views, activities, or ambiance, use image_themes instead. Do not use image-theme values here, including: - KIDS_CLUB_INDOORS - CHILDREN_PLAYGROUND_OUTDOORS - AQUA_PARK - GOLF - SKIING Use: - SPA_AND_WELLNESS_CENTRE for spa - HOT_TUB_JACUZZI for hot tub or jacuzzi High-confidence mappings: - pool -> SWIMMING_POOL - restaurant -> RESTAURANT - free parking -> FREE_PARKING - gym/fitness -> FITNESS_CENTRE - beach access / on the beach -> BEACH - beachfront / directly on the beach -> BEACHFRONT Do not infer FAMILY_ROOMS from family-friendly or traveling with kids.

A list of specific hotel names to search for availability and pricing. ONLY use this field when the user has explicitly mentioned exact hotel names in their message (e.g., "check prices at Hilton Paris Opera and Ritz Paris"). Do NOT infer or guess hotel names from a destination or area description. Rules: - MUTUALLY EXCLUSIVE with destination and coordinates — when hotel_names is provided, you MUST NOT include destination or coordinates fields, and vice versa. - Use the canonical English name of each hotel (e.g., "Hilton Paris Opera", "Ritz Paris"). - Each name should be a short canonical hotel name without branch qualifiers (e.g., "NH Collection Krasnapolsky" not "NH Collection Grand Hotel Krasnapolsky Amsterdam"). - If the user mentions both a destination AND specific hotel names, use hotel_names only (the names are more specific). - If the user asks for "hotels in Paris" or "best hotels near the Eiffel Tower" without naming specific properties, use destination or coordinates instead — NOT this field.

Visual themes for property card images. Use this for what the user wants to SEE in photos. This is a presentation field, not a hard search filter. Use ONLY exact image theme enum values, never facility names. Categories: - Views: CITY_VIEW, SEA_VIEW, MOUNTAIN_VIEW, RIVER_LAKE_VIEW, GARDEN_GARDEN_VIEW - Water: BEACH, SWIMMING_POOL, OUTDOOR_SWIMMING_POOL, INDOOR_SWIMMING_POOL - Dining: RESTAURANT_COMMON_DINING_AREA, BREAKFAST, FOOD, COFFEE_TEA_FACILITIES, KITCHEN_OR_KITCHENETTE - Wellness: SPA_WELLNESS_MASSAGE, JACUZZI_HOT_TUB - Outdoor: NATURAL_LANDSCAPE, BALCONY_TERRACE, ROOFTOP - Kids: KIDS_CLUB_INDOORS, CHILDREN_PLAYGROUND_OUTDOORS, AQUA_PARK - Room: BED, TWIN_BED_2_BEDS, FIREPLACE - Activities: GOLF, SKIING - Ambiance: ROMANCE Rules: - Populate independently from facilities. - Add themes the user explicitly wants to see, or clearly implies visually. - Use destination context only to choose the right view after a visual cue exists, such as view, balcony, terrace, rooftop, scenic, overwater villa, honeymoon, retreat, cabin, cottage, chalet, or villa. - Then map destination context: urban -> CITY_VIEW, coastal/island -> SEA_VIEW, mountain/ski -> MOUNTAIN_VIEW, lakeside -> RIVER_LAKE_VIEW. - Do not add view themes from destination alone. - Include NATURAL_LANDSCAPE for countryside, rural, mountain, lakeside, scenic, garden, cabin, cottage, chalet, or retreat settings. - Include ROMANCE only for explicit romantic context such as honeymoon, anniversary, romantic trip, or couples getaway. - For pool, include SWIMMING_POOL plus INDOOR_SWIMMING_POOL and OUTDOOR_SWIMMING_POOL unless the user limits the type. - Map room features directly: bed -> BED, twin beds -> TWIN_BED_2_BEDS, fireplace -> FIREPLACE, kitchen/kitchenette -> KITCHEN_OR_KITCHENETTE. - Exclude negated themes. Return [] if nothing clearly matches.

Use this when the user mentions a preference on the meals that need to be included at the property stay. Only include the meal plan if explicitly mentioned by the user; otherwise leave this empty. IMPORTANT: Map natural-language meal requests to this field, NOT to facilities. For example, "I want breakfast" → breakfast_included.

The minimum review score of the hotel the user is looking for. Only return a value if the user explicitly mentions the review score level they are looking for. If the user explicitly mentions 'superb/excellent review score', the value should be 9. If the user explicitly mentions 'High/Very good review score', the value should be 8. If the user explicitly mentions 'Good review score', the value should be 7. Else return null, including cases when the user doesn't say anything about review scores.

Number of adult guests for the entire stay across all rooms.

The total number of separate rooms needed for the stay.

Price per night range for the given search.

Limit search results to accommodations with specific star ratings. Populate ONLY when the user explicitly requests a star rating (e.g., “5-star hotels”, “3 or 4 stars”). Array of integers from 1 to 5. The search matches ANY rating in the array (OR logic). For ranges like “3 stars or higher”, include [3, 4, 5].

The user's locale in BCP 47 / ISO 639 format (e.g., 'en-us', 'fr', 'de', 'ja'). Use the locale that best matches the language the user is communicating in, unless the user explicitly asks the LLM to respond in a different language. In that case, use that language.

A short and concise natural language query in English that strictly and only contains the requirements explicitly mentioned by the user. Hard requirements: Absolutely cannot use any personally identifiable information (like personal names, dates of birth, identification numbers, bank account numbers, etc.). Absolutely must not include specific location details (street names, street numbers, or specific house/apartment names); use only general location identifiers (city, neighborhood, area, or a major landmark). You are not allowed to include default parameters in the query, only use facts the user explicitly mentioned. Be written from the user perspective, matching the user’s style. Include all explicitly stated requirements (e.g., facilities, travel date/period, location) and explicitly stated secondary needs (e.g. romantic / luxurious / maybe a spa). Resolve multi-turn conversation context into a single, complete request. Be descriptive, concise, and specific, but do not add extra constraints or qualifiers the user didn’t explicitly ask for.

Initial layout mode for the accommodation results widget. Set to "MAP" when location is the primary axis of the user's choice — e.g. explicit map request, coordinate search, proximity to a landmark, neighborhood, area, or transit hub, or comparing areas.

The Booking.com property ID to query against. CRITICAL: Do not hallucinate IDs; they must be retrieved from the current user interface context.

The natural language question from the user. Resolve any conversational context or pronouns into a standalone query. This field must be written in English. Examples: 'How much is parking per day?', 'Which of these is better for small children?', 'What is the size of the double bed?'. The tone should remain helpful and inquisitive.

The ISO 3166-1 alpha-2 country code for the user's location in lowercase. The following country codes are not supported: [ir, ru, by, cu, kp, sy]. Do not call this tool if the user is from one of the non-supported countries.

Filter attractions by category. Allowed values: "tours" (Tours & Sightseeing), "museums_arts_culture" (Museums, Arts & Culture), "nature_outdoor" (Nature & Outdoor), "entertainment_tickets" (Entertainment & Tickets), "food_drinks" (Food & Drinks), "travel_services_rental" (Travel Services & Rental), "workshop_classes" (Workshops & Classes). Results matching ANY selected category are returned.

Geographic coordinates for a location-based search. Use this instead of destination when: - The user wants accommodations near a specific non-accommodation place (hospital, office, university, restaurant, venue, gym, etc.) — estimate the latitude and longitude of that place. - The user provides an exact address or a location too specific for a city/neighborhood name. - The user mentions a small, locally-known area within a city (a specific intersection, market, circle, or micro-neighborhood that is unlikely to be recognized by a global search engine) — estimate the coordinates of that area. Mutually exclusive with destination — provide either destination OR coordinates, not both.

The ISO 4217 currency code for displaying prices in uppercase. Only fill this field if the user explicitly mentions the desired currency.

The place name to search for accommodations, in English. Must be a single, specific location — not a sentence, question, or list of places. Supported types: city ("Paris, France"), neighborhood ("Trastevere, Rome"), region ("Tuscany, Italy"), hotel name ("Hilton Paris Opera"), airport IATA code ("JFK"), landmark ("Eiffel Tower, Paris"), transit station ("Central Station, Amsterdam"). Rules: - One location only. Never comma-separate multiple cities or regions. - Include the parent region or country when the name is ambiguous (e.g., "Paris, Texas" not just "Paris", "Cambridge, MA" not just "Cambridge"). - Use the canonical English name with proper diacritics (e.g., "Córdoba, Spain", "Cancún, Mexico"). - If the user mentions a vague area within a city, resolve it to the most specific recognizable place name (e.g., "near the Louvre" → "Louvre, Paris"). - Never include dates, filters, or natural language queries (e.g., "hotels in Paris on June 5" is wrong — just pass "Paris, France"). - If the user mentions a specific place that is NOT an accommodation (not a hotel, hostel, resort, apartment, lodge, B&B, or villa), use coordinates instead of this field. This includes hospitals, restaurants, offices, schools, gyms, shops, and other non-lodging locations. - For small or locally-known sub-areas within a city (e.g., a specific intersection, circle, or micro-neighborhood), prefer coordinates to pinpoint the location. If coordinates are not feasible, use the well-known parent district or city instead (e.g., "Bangalore" instead of "Anand Rao Circle, Bangalore"). - When the user asks for a specific hotel by name, use a short canonical name without branch qualifiers or suffixes (e.g., "Hilton Paris Opera" not "Hilton Paris Opera Hotel & Spa"). - Mutually exclusive with coordinates.

The end date for attractions availability in ISO 8601 format (YYYY-MM-DD). This must be after the start date and within 90 days of the start date.

Minimum review score to filter attractions (0-5 scale). Populate ONLY when the user explicitly requests a minimum review quality. If not specified, results are not filtered by review score.

The start date for attractions availability in ISO 8601 format (YYYY-MM-DD).

The user's locale in BCP 47 / ISO 639 format (e.g., 'en-us', 'fr', 'de', 'ja'). Use the locale that best matches the language the user is communicating in, unless the user explicitly asks the LLM to respond in a different language. In that case, use that language.

A short and concise natural language query in English that strictly and only contains the requirements explicitly mentioned by the user. Hard requirements: Absolutely cannot use any personally identifiable information (like personal names, dates of birth, identification numbers, bank account numbers, etc.). Absolutely must not include specific location details (street names, street numbers, or specific house/apartment names); use only general location identifiers (city, neighborhood, area, or a major landmark). You are not allowed to include default parameters in the query, only use facts the user explicitly mentioned. Be written from the user perspective, matching the user's style. Include all explicitly stated requirements (e.g., categories, travel dates, location, group composition) and explicitly stated secondary needs (e.g. family-friendly / outdoor / cultural). Resolve multi-turn conversation context into a single, complete request. Be descriptive, concise, and specific, but do not add extra constraints or qualifiers the user didn't explicitly ask for.

Drop-off datetime in ISO format (e.g., 2025-11-10T11:05:00).

Pick-up datetime in ISO format (e.g., 2025-11-10T11:05:00).

The ISO 3166-1 alpha-2 country code for the user's location in lowercase. The following country codes are not supported: [ir, ru, by, cu, kp, sy]. Do not call this tool if the user is from one of the non-supported countries.

The ISO 4217 currency code for displaying prices in uppercase. Only fill this field if the user explicitly mentions the desired currency.

Driver age. Affects the availability and price of the rental products.

Three-letter IATA airport code for the drop-off location (e.g., JFK, LAX, LHR). Provide either this or `dropoff_location`, but not both. If not provided, pickup_location or pickup_airport_iata used by default.

The name of the drop-off location. It should be a city name, hotel name, or airport. Use dropoff_location or dropoff_airport_iata, not both. If not provided, pickup_location or pickup_airport_iata used by default.

Filter car rental results by specific features such as transmission type, air conditioning, mileage options, car categories, depot location, number of seats, and suppliers.

Three-letter IATA airport code for the pick-up location (e.g., JFK, LAX, LHR). Provide either this or `pickup_location`, but not both.

The name of the pick-up location. It should be a city name, hotel name, or airport. Use pickup_location or pickup_airport_iata, not both.

How to order the search results. Omit this field entirely to use the recommended sort order. Only provide when the user explicitly requests sorting by price or review score.