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.