ALL Accor

Check-in date in the format yyyy-MM-dd (UTC). IMPORTANT: send {Current day + 7} by default

Check-out date in the format yyyy-MM-dd (UTC). IMPORTANT: ONLY Send {Check-in date + 1} IF NOT SPECIFIED BY USER

User's country of residence in ISO 3166-1 alpha-2 format (e.g., 'FR', 'US', 'CA', 'DE', 'GB'). IMPORTANT: If not known, send FR

User currency for pricing (e.g., 'EUR', 'USD'). IMPORTANT: If not known, send EUR

Bounding box coordinates in WGS84 format [min_lon, min_lat, max_lon, max_lat]. max_lon has to be strictly superior to min_lon. max_lat has to be strictly superior to min_lat. Example for Paris city center: [2.224122, 48.815575, 2.469760, 48.902156]. Allow only coordinates at the level of city districts, cities, or regions within a country (e.g., Alsace, Massachusetts), and reject any broader coordinates such as countries or world regions.

The user's destination city and country (e.g., Paris, France)

Maximum number of stars for hotels to display, send 5 by default

Minimum number of stars for hotels to display, send 0 by default

IMPORTANT: Send 'PUBLIC' by default. Determines which rates to fetch: 'PUBLIC' shows publicly available rates, 'MEMBER' restricts to ALL member-only offers

Mandatory: SEND known User discussion language code in ISO 639-1 format (2 characters: 'en', 'fr', 'es', 'de', 'it', 'ja', etc.). Special case: use 'pt-br' for Brazilian Portuguese.

Number of adults staying (defaults to 1). IMPORTANT: X People/Person DOES NOT MEAN X Adults. Please check with user

Filter by hotel brands (brand codes). Generic codes auto-expand to related specialized brands (e.g., NOV -> SUI, NOL; IBH -> IBB, IBS; MER -> BME, MEI, MEL; SOF -> SOL, SO; ADG -> ADA, ADP; SWI -> SWL; MOV -> MOL).

List of children’s ages. This field contains the list of children’s ages and must only include ages explicitly provided by the user. The assistant must never infer or assume ages. If the user mentions having children but does not specify each child’s age, the assistant must ask for the missing ages before calling the tool. If no children are mentioned, this field must be an empty array. Each child must have exactly one integer age between 0 and 17

Filter hotels by MAXIMUM price PER STAY (not night) of hotels to display. If the price is "around X" make it deviation of 25% more

Filter hotels by MINIMUM price PER STAY (not night) of hotels to display. If the price is "around X" make it deviation of 25% less

Page number for pagination (defaults to 0)

Natural language description of desired hotel characteristics and amenities (e.g., "with spa", "rooftop pool", "city view", "near attractions"). MUST be in English only. DO NOT include booking details like dates, guest counts, or location/destination information - these are specified in separate parameters. Focus only on property features, amenities, atmosphere, or nearby points of interest. Examples: romantic hotel with spa, family-friendly near beach, business hotel with conference rooms,...

Check-in date in the format yyyy-MM-dd (UTC). IMPORTANT: send {Current day} IF NOT SPECIFIED BY USER and if date is between the 01 of january and today, send the date for next year

Check-out date in the format yyyy-MM-dd (UTC). IMPORTANT: ONLY Send {Check-in date + 1} IF NOT SPECIFIED BY USER

User currency for pricing (e.g., 'EUR', 'USD'). IMPORTANT: If not known, send EUR

The user's destination city and country (e.g., Paris, France)

Bounding box coordinates in WGS84 format [min_lon, min_lat, max_lon, max_lat]. max_lon has to be strictly superior to min_lon. max_lat has to be strictly superior to min_lat. Example for Paris city center: [2.224122, 48.815575, 2.469760, 48.902156]. Allow only coordinates at the level of city districts, cities, or regions within a country (e.g., Alsace, Massachusetts), and reject any broader coordinates such as countries or world regions.

Determines which rates to fetch: 'PUBLIC' shows publicly available rates, 'MEMBER' restricts to ALL member-only offersUse user's preference. IMPORTANT: If the user did not specify, send 'PUBLIC' by default.

Mandatory: SEND known User discussion language code in ISO 639-1 format (2 characters: 'en', 'fr', 'es', 'de', 'it', 'ja', etc.). Special case: use 'pt-br' for Brazilian Portuguese.

User's country of residence in ISO 3166-1 alpha-2 format (e.g., 'FR', 'US', 'CA', 'DE', 'GB'). IMPORTANT: If not known, send FR

The view mode for displaying hotel search results. Use "map" when the user's intent is spatial or location-based: - Searching near a landmark or point of interest ("closest to the Louvre", "near Châtelet") - Refining or expanding a geographic search area ("less than 2km", "enlarge to downtown") - Comparing hotels by distance or proximity ("which is closest to the metro") - Asking about a specific hotel's location relative to something ("how far from the metro") Use "list" in all other cases. Use "list" by default.

Number of adults staying (defaults to 1). IMPORTANT: X People/Person DOES NOT MEAN X Adults. Please check with user

Filter by hotel brands (brand codes). Generic codes auto-expand to related specialized brands (e.g., NOV -> SUI, NOL; IBH -> IBB, IBS; MER -> BME, MEI, MEL; SOF -> SOL, SO; ADG -> ADA, ADP; SWI -> SWL; MOV -> MOL).

List of children’s ages. This field contains the list of children’s ages and must only include ages explicitly provided by the user. The assistant must never infer or assume ages. If the user mentions having children but does not specify each child’s age, the assistant must ask for the missing ages before calling the tool. If no children are mentioned, this field must be an empty array. Each child must have exactly one integer age between 0 and 17

Best-offer filters grouped by domain

Semantic search query matched against static hotel descriptions stored server-side. Use to refine results beyond what other parameters filter. Include ONLY: physical amenities, property style/atmosphere, location qualities, target experience (e.g., "romantic spa hotel with sea view", "family resort with waterpark"). Exclude: anything covered by other parameters (destination, dates, guests, price, stars, brands) and any dynamic data not in hotel descriptions (guest reviews, scores, promotions, availability). English only. Leave empty if no specific property traits desired.

Ordered list of sort criteria applied to hotel results. The first element has the highest priority; subsequent elements break ties between hotels that share the same value on the previous criterion. When omitted or empty, hotels are displayed in the order returned by the API (no sorting applied). Default directions when omitted: price → asc (cheapest first), review → desc (best rated first), stars → desc (most luxurious first). Examples: - "best rated and cheapest hotels": [{criterion: "review"}, {criterion: "price"}] - "best value for money" (quality/price ratio): [{criterion: "stars"}, {criterion: "price"}] - "cheapest hotels": [{criterion: "price"}] - "most luxurious": [{criterion: "stars"}]

A concise synthesis of the user's original request in the user's language. Summarize what the user is looking for including destination, dates, preferences, and any specific requirements they mentioned. This is used for analytics and monitoring purposes. Example: "Looking for a 4-star hotel in Paris near the Eiffel Tower for 2 adults, check-in March 15, budget around 200€/night"