> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gojinko.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Hotel Reviews

> Fetch the guest review summary, per-category scores and recent reviews for a single hotel

Answer what guests say about a property after a search result or a hotel\_details lookup catches the user's attention. Useful for questions like "what do guests say about this hotel", "is it clean", "how is the location" or "is the staff friendly". Returns the overall guest score and review count, a pros/cons summary, per-category scores and the most recent individual reviews.

> **Tool description (what the LLM sees)**
>
> ```text theme={null}
> Fetch the guest review summary and recent reviews for a single hotel.
>
> Use this AFTER hotel_search or hotel_details, when the user asks what guests say about a hotel, or how it scores on cleanliness, location, staff or value.
>
> REQUIRED:
> - hotel_id: the hotel_id from hotel_search, or the id from hotel_details, passed exactly as returned
>
> OPTIONAL:
> - limit: number of recent reviews to return (1-50, default 10)
> - offset: number of recent reviews to skip, for paging (default 0)
>
> RESPONSE:
> - hotel: { id, name, rating (overall guest score out of 10), review_count }
> - summary: { pros[], cons[], categories[] ({ name, rating, description }), updated_at }, or null when the hotel has no review summary
> - reviews[]: most recent first, each with headline, score (out of 10), pros, cons, date, language and reviewer_name when available
> - page: { limit, offset, total_count } (total_count is null when unknown)
>
> Notes:
> - Read-only. Does not affect the trip or quote.
> - The review source is not attributed; present the scores and reviews as guest reviews.
> - Never invent reviews or scores the response does not contain. When reviews[] is empty, say no recent reviews were returned.
> ```

## Parameters

| Name | Type | Required | Description |
| - | - | - | - |
| `hotel_id` | `string` | Yes | The hotel\_id of a hotel from hotel\_search, or the id hotel\_details returns, passed exactly as returned. It is an opaque string: do not parse or build it. |
| `limit` | `integer` | No | Max recent reviews to return (1-50). Default 10. |
| `offset` | `integer` | No | Number of recent reviews to skip, for pagination. Default 0. |
| `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. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.