get_hotels
ChatGPTFetch detailed information for hotels by ID. Use this to get data for specific hotel IDs from previous search results. Specify which data blocks to fetch (details, offers, rooms, reviews, etc.). Use the search tool for location-based discovery.
get_hotels
ChatGPTFetch detailed information for hotels by ID. Use this to get data for specific hotel IDs from previous search results. Specify which data blocks to fetch (details, offers, rooms, reviews, etc.). Use the search tool for location-based discovery.
search_hotels
ChatGPTSearch for hotels and accommodations by location, coordinates, or hotel ID. Pass any user-provided location/address/landmark to the query parameter - the geocoding service will resolve it. IMPORTANT: When query mentions "family" or "families", exclude hostels using filters.excludePropertyTypes: ["hostel"]. Place filter parameters inside the filters object. RESULT HANDLING: Results are ranked with best filter matches first. If filters cannot be fully satisfied, partial matches are returned. Always display results to the user immediately. Do NOT retry or paginate unless user explicitly requests more. When hasMoreResults=false, all matching hotels have been returned. UI UPDATE RULE: When a hotel UI widget is already displayed from a previous search, you MUST call this tool again for any user request that changes the search criteria (filters, dates, location, guests, sorting, etc.). Do NOT answer filter/refinement questions from memory or prior results - always call the tool to refresh the UI with updated results.
search_hotels
ChatGPTSearch for hotels and accommodations by location, coordinates, or hotel ID. Pass any user-provided location/address/landmark to the query parameter - the geocoding service will resolve it. IMPORTANT: When query mentions "family" or "families", exclude hostels using filters.excludePropertyTypes: ["hostel"]. Place filter parameters inside the filters object. RESULT HANDLING: Results are ranked with best filter matches first. If filters cannot be fully satisfied, partial matches are returned. Always display results to the user immediately. Do NOT retry or paginate unless user explicitly requests more. When hasMoreResults=false, all matching hotels have been returned. UI UPDATE RULE: When a hotel UI widget is already displayed from a previous search, you MUST call this tool again for any user request that changes the search criteria (filters, dates, location, guests, sorting, etc.). Do NOT answer filter/refinement questions from memory or prior results - always call the tool to refresh the UI with updated results.
search_hotels_availability
ChatGPTDiscover WHEN to go — date-axis tool. Returns a price calendar of cheapest rates for each check-in date across a date range, so the user can pick the best dates to travel. Use this when the user is flexible on dates and wants to compare across them: "cheapest week in May", "price calendar for June", "when is Paris cheaper", "best dates to fly to Tokyo this fall", "should I go in May or June". Do NOT use this tool for: (a) fixed-date searches ("hotels in Paris for June 1-3") — use search_hotels; (b) "is this hotel a good deal?" / value or historical-trend questions — use search_hotels with include=["analytics"]; (c) hotel discovery / filtering by amenities or features — use search_hotels. IMPORTANT: hotel selection — by default we pick the top hotels by popularity, which gives a representative date trend across mainstream options but NOT the absolute floor. When the user asks for the cheapest possible trip ("cheapest", "lowest price", "willing to compromise on quality"), pass sortField: "price" with sortOrder: "ascending" so the calendar reflects the actual price floor, optionally with filters.guestRating: [7, 8, 9, 10] to keep quality reasonable. Without this the calendar can overstate prices by 30-90% on most dates. IMPORTANT: When query mentions "family" or "families", exclude hostels using filters.excludePropertyTypes: ["hostel"].
search_hotels_availability
ChatGPTDiscover WHEN to go — date-axis tool. Returns a price calendar of cheapest rates for each check-in date across a date range, so the user can pick the best dates to travel. Use this when the user is flexible on dates and wants to compare across them: "cheapest week in May", "price calendar for June", "when is Paris cheaper", "best dates to fly to Tokyo this fall", "should I go in May or June". Do NOT use this tool for: (a) fixed-date searches ("hotels in Paris for June 1-3") — use search_hotels; (b) "is this hotel a good deal?" / value or historical-trend questions — use search_hotels with include=["analytics"]; (c) hotel discovery / filtering by amenities or features — use search_hotels. IMPORTANT: hotel selection — by default we pick the top hotels by popularity, which gives a representative date trend across mainstream options but NOT the absolute floor. When the user asks for the cheapest possible trip ("cheapest", "lowest price", "willing to compromise on quality"), pass sortField: "price" with sortOrder: "ascending" so the calendar reflects the actual price floor, optionally with filters.guestRating: [7, 8, 9, 10] to keep quality reasonable. Without this the calendar can overstate prices by 30-90% on most dates. IMPORTANT: When query mentions "family" or "families", exclude hostels using filters.excludePropertyTypes: ["hostel"].
