Radisson Hotels

Shows a directory of countries or cities with Radisson Hotels, or lists available amenity filter keys. Use when user asks what destinations are available, or to verify a destination exists before searching. If user shows search intent and has a country, use the search_hotels tool instead of this one. Directory tool only: discover which countries/cities have Radisson presence, or which amenities are available. Use ONLY for destination-listing or amenity-discovery intent, not for hotel search. Never use this tool when user asks for hotels, prices, availability, ranking, or booking help. Without a country argument (type='destinations'), returns a list of all countries with hotel counts. With a country argument (type='destinations'), returns cities in that country with hotel counts. With type='amenities', returns all available amenity filter keys and their display titles. Use type='amenities' to discover valid keys before filtering by amenities in search_hotels. Example intents for this tool: - 'Which countries does Radisson operate in?' - 'What cities in Spain have Radisson hotels?' Example intents for search_hotels tool instead of this one: - 'Find me Radisson hotels in Spain' - 'What hotels are available in Lisbon?'

destinations_directory

Returns in-depth practical detail for ONE hotel that search_hotels does not carry: the full amenity list with caveats, parking, pet and accessibility policies, and the hotel restaurant — cuisine types, opening hours per meal, dining services (buffet, à la carte, gluten-free, halal, room service), allergen information and a direct restaurant phone and email. Use this when the user asks anything specific about one hotel they have already identified. Example intents: 'what time is breakfast?', 'does it have gluten-free options?', 'can I bring my dog?', 'is parking free?', 'what kind of food do they serve?', 'is it wheelchair accessible?', 'what's the restaurant's phone number?' Requires hotelId. If you do not have one, call search_hotels first and use the id it returns for that hotel — never guess an id. Do NOT use this tool to search for or compare hotels, and do NOT use it to show prices or availability: use search_hotels for that. Coverage varies by hotel. When a detail is absent from the response, tell the user it is not published rather than saying the hotel does not offer it.

get_hotel_details

Search for Radisson hotels in a city or country and display them on an interactive map for the user. This is the PRIMARY tool for hotel or property search/display intent, including prices, availability, ranking, and recommendations. Call this tool EXACTLY ONCE per user request. For several cities in the same country, pass them ALL together in the 'destination' array (e.g. ['Madrid', 'Barcelona']) — never make one call per city, and never call the tool more than once for the same request (extra calls render duplicate maps). Do not ask for additional details first unless both destination and country are missing. If both destination and country are missing, ask exactly one brief follow-up question to get it, then call the tool. Rules: (1) Follow input schema and field descriptions exactly; never invent values. (2) Omit unknown or uninferrable optional fields entirely (no empty strings, placeholders, or 0 as placeholder). (3) Keep coordinates separated: use 'destinationCoordinates' as center for destination and 'proximityCoordinates' only for near/within requests. (4) Set 'minPrice'/'maxPrice' only when user explicitly provides price or budget. (5) 'brands' must ALWAYS include ALL brand keys by default. Only remove brands from the list when the user explicitly names one (e.g. 'Radisson Blu' → only ["rdb"], 'art\'otel' → only ["art"], 'Park Plaza' → only ["pph"]).

search_hotels

Show a single Radisson hotel booking card. Use this when user asks to book a specific hotel now. This tool does not initiate or complete a booking, it only shows hotel details and booking link in single card format. User is expected to click through to complete booking on Radisson website. Pass either hotelId (preferred if known) or hotelName. If both are available, pass both.

start_hotel_booking

Records one user interaction event generated by the Radisson hotel widget UI: booking_cta_clicked, map_marker_clicked, hotel_card_clicked, hotel_details_opened, hotel_link_clicked or full_screen_view_opened. Each event carries the event name, the widget placement it originated from, a per-interaction id and, when the interaction refers to a specific hotel, that hotel's id and name. No personal, account or booking data is recorded. This tool is called exclusively by the front-end widget through the app bridge. It is not exposed to or invoked by the assistant and it is not part of the hotel search, booking or directory flows. It writes this interaction telemetry to the connector's own analytics store for product analytics. It returns only an acknowledgement ({ tracked: true }); it returns no hotel data and changes no user, booking or account state.

track_ui_event