Hotel Details

Pull the full marketing and operational profile of a single property after a search result catches the user’s attention. Useful for questions like “what amenities does this hotel have”, “is there a pool on site”, or “what amenities does the deluxe room have”. Returns the gallery, facilities, room metadata, and property policies. For refundability and cancellation terms, read the selected rate from hotel_search.

Tool description (what the LLM sees)

Fetch rich metadata (gallery, facilities, policies, per-room metadata) for a single hotel.

Use this AFTER hotel_search returns a list of hotels and the user wants a closer look at one.

REQUIRED:
- hotel_id: the hotel_id of a hotel from hotel_search, passed exactly as returned

OPTIONAL:
- checkin, checkout (YYYY-MM-DD): accepted; the platform does not use them yet.

RESPONSE:
- hotel: { id, name, star_rating, address, images[], facilities[], policies[] }
- rooms[]: per-room metadata, each with name + description, and max_adults / max_children (when available; max_children 0 means the room takes no children)

Notes:
- Read-only. Does not affect the trip or quote.
- Property policies and room metadata are not rate cancellation terms. Read refundability and the cancellation schedule from the selected hotel_search rate.
- Independent of pricing, call hotel_search first to get live rates with offer tokens.

Parameters

Name	Type	Required	Description
`hotel_id`	`string`	Yes	The hotel_id of a hotel from hotel_search, passed exactly as returned. It is an opaque string: do not parse or build it.
`checkin`	`string`	No	Check-in date (YYYY-MM-DD). Accepted; the platform does not use it yet.
`checkout`	`unknown`	No	Check-out date (YYYY-MM-DD). Accepted; the platform does not use it yet.
`user_intent`	`string`	No	The end user’s current request in their own words, e.g. “help me with my travel plans”. Pass it as-is when short; otherwise condense the goal and constraints into 1-2 sentences. Strip personal identifiers (names, emails, phone numbers, addresses, payment details), replace them with placeholders like “[name]”. Optional. Jinko uses it to understand demand, and hotel_search uses it to rank hotel results against what the user asked for (e.g. “quiet, with a gym, near Times Square”), so keep the user’s stated preferences in it.

Examples

Fetch full details for a single hotel returned by hotel_search:

{
  "name": "hotel_details",
  "arguments": {
    "hotel_id": "lpe2264"
  }
}

Optional dates (accepted but currently unused): checkin and checkout do not change the returned details. Omit them when fetching the property profile.

{
  "name": "hotel_details",
  "arguments": {
    "hotel_id": "lpe2264",
    "checkin": "2027-07-15",
    "checkout": "2027-07-18"
  }
}

The response carries hotel-level metadata (images, facilities, policies) plus per-room details (room name + description). Read-only: doesn’t affect a trip or quote.

Introduction

Flights

Hotels

Cars

Trip & Payment

Marketing claim

Parameters

Examples

​Parameters

​Examples

Parameters

Examples