Hotel Details - Jinko Platform

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 is the cancellation policy on the deluxe room”. Returns the gallery, facilities, room metadata, and policies in one payload.

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. Pass the hotel_id from a hotel_search result.

REQUIRED:
- hotel_id: string (from a hotel_search offer)

OPTIONAL:
- checkin, checkout (YYYY-MM-DD): accepted for cache-key alignment; currently ignored by the BFF.

RESPONSE:
- hotel: { id, name, star_rating, address, images[], facilities[], policies[] }
- rooms[]: per-room metadata, each with name + description (when available)

Notes:
- Read-only. Does not affect the cart or quote.
- Independent of pricing, call hotel_search first to get live rates with offer tokens.

Parameters

Name	Type	Required	Description
`hotel_id`	`string`	Yes	Hotel ID (from a prior hotel_search offer).
`checkin`	`string`	No	Check-in date (YYYY-MM-DD). Accepted for future cache-key alignment; currently unused by the BFF.
`checkout`	`string`	No	Check-out date (YYYY-MM-DD). Accepted for future cache-key alignment; currently unused by the BFF.
`user_intent`	`string`	No	The end user’s current request in their own words, e.g. “find a cheap flight to Tokyo in mid-June”. 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 and never changes the result of the call; Jinko uses it to understand demand and improve results.

Examples

Fetch full details for a single hotel returned by hotel_search:

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

With dates passed for cache alignment:

{
  "name": "hotel_details",
  "arguments": {
    "hotel_id": "lpe2264",
    "checkin": "2026-07-15",
    "checkout": "2026-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.