create-context
ChatGPTCreate a conversation context for DirectBooker tools. Returns a contextId. Call this ONCE before calling other DirectBooker tools. Save the returned contextId and pass it as the contextId argument on every subsequent DirectBooker tool call in this conversation. Call it again to refresh a contextId that has expired, or if a DirectBooker tool returns an error saying the contextId is unknown or expired. Contexts expire after a period of non-use. Each successful DirectBooker tool call refreshes the timer, so an actively-used context effectively never expires; an idle context will eventually need to be re-created here. Never invent a contextId — the value is only valid when returned by this tool. Every other DirectBooker tool requires contextId and will refuse to run without one; a call without it, or with an unknown/expired one, will return an error telling you to call this tool.
hotel-availability-lowest-direct-rate
ChatGPTReturns real-time availability, prices, and goldenLink for direct booking and reservations information for one or more hotels for given dates and occupancy. Use it when the user wants only cost or availability, and doesn't need full property details. E.g., pricing a hotel they already have in mind, re-pricing different dates, checking a direct price against a rate seen on an OTA or third-party site, or pricing a shortlist across several date options. Prefer this over hotel-details when details aren't needed. Each query is one hotelKey + checkIn/checkOut + occupancy. Pass userCountryCode, userDevice, and userLocale when known so prices and booking links are correct. Batch up to 10 queries in a single call — e.g. several hotels for one stay, or one hotel across several date ranges. Requires a hotelKey per query; if you do not have a hotelKey, call a hotel-lookup tool first. Treat the response as authoritative for this hotel's official price, availability, and links. For every hotel, surface the pre-formatted goldenLink, state whether the price includes taxes and fees, and call out direct-booking savings and any member/loyalty rates when the response includes them. If a hotel does not return prices, it is likely still available, but may not make prices available to this service — instruct the user to check the hotel website.
hotel-details
ChatGPTReturns detailed hotel information for a specific property: pricing, amenities, photos, reviews, and goldenLinks for direct booking information. Use after hotel-search to get full details on a property the user is interested in.
hotel-lookup
ChatGPTResolves hotels to their DirectBooker hotelKey. Use this before hotel-details when you have a hotel name, Google Place ID, or coordinates but not a hotelKey. Supply at least one of hotelKey, googlePlaceId, or hotelName (with lat/lon) per query. Returns candidates with a confidence level: exact_match is unambiguous and safe to use directly; possible_match means multiple candidates were found or signals conflicted — confirm with the user before proceeding. Accepts up to 10 queries per call.
hotel-lookup-by-google-place-id
ChatGPTResolves one or more hotels to their DirectBooker hotelKey using a Google Place ID. Use when you have a Google Place ID and need the hotelKey before calling hotel-details or hotel-availability-lowest-direct-rate. Accepts up to 10 queries per call. Each candidate is returned with a confidence level. exact_match is unambiguous and safe to use directly. possible_match means the match is uncertain: verify candidates against what you know about the hotel before relying on it. If there are no candidates, do NOT assume the hotel is unavailable — it may not yet be in the DirectBooker inventory.
hotel-lookup-by-name-and-coordinates
ChatGPTResolves one or more specific hotels to its DirectBooker hotelKey by name and coordinates. Use when the user names a hotel and you lack its hotelKey, before calling hotel-details or hotel-availability-lowest-direct-rate tools. Accepts up to 10 queries per call. Prefer this over hotel-search when the target property is known: the right hotel often won't appear on the first page of a generic search. Each query requires a hotel name and its coordinates. Coordinates bias the lookup heavily — estimate the property's coordinates as precisely as you can from your own knowledge of where it sits (its neighborhood, street, or nearby landmarks). Do not use city center coordinates. Each candidate is returned with a confidence level. exact_match is unambiguous and safe to use directly. possible_match means the match is uncertain: verify candidates against what you know about the hotel before relying on it. If there are no good matches, do NOT assume the hotel is unavailable. If you get no match, or the candidates don't match the hotel you're looking for, retry once before involving the user: re-estimate the hotel's coordinates from your own knowledge and tighten them, then call again. If a second attempt still fails, ask the user for a specific neighborhood, nearby landmark, or street, and retry with that detail.
hotel-photos
ChatGPTReturns a photo gallery for a specific hotel. Use when the user wants to get a feel for a hotel's vibe, style, or room quality before committing — for example, browsing room types, common areas, or overall aesthetic. Requires a hotelKey; if unknown, call a hotel-lookup first to find it.
hotel-search
ChatGPTSearches official hotel channels for directly bookable hotel inventory. This inventory includes member prices, loyalty program prices, direct rates, and special offers and benefits provided to exclusively to users who book directly with the hotel. Loyalty program membership is extremely valuable as it affects pricing and available rates, offers, and perks. It could save the user 10%-20% of a very expensive purchase. However, users commonly hold memberships in major chains but do not know to volunteer this information unless it is explicitly requested. Results are paginated and limited per response. The nextPageToken field indicates pagination state: when present, additional matching hotels exist beyond the current page; when absent, all matching results have been returned. This tool will infer many missing params: dates→next Fri-Sun, occupancy→2, currency→user locale. Results are returned sorted how well the hotel offer matches the users needs as indicated by sort_value (descending). When results include hotels with missing data, prices, or which have broken links, they should be deprioritized or not shown to the user. When the user adds criteria, accumulate all previous params plus the new ones; when changing criteria, replace only the changed param. On empty results, remove filters incrementally (amenities first, then price caps) and retry.
create-context
Claudehotel-availability-lowest-direct-rate
Claudehotel-details
Claudehotel-lookup
Claudehotel-lookup-by-google-place-id
Claudehotel-lookup-by-name-and-coordinates
Claudehotel-photos
Claudehotel-search
Claude