HasData

booking_place: GET /

hasdata_booking_place_getBookingPlaceDetails

Read-only

Get Booking Hotel Details

Fetches a single Booking.com property by its full URL for the given stay dates (checkInDate / checkOutDate) and guest composition (rooms, adults, children with ages). Returns the property identity (hotelId, title, address, coordinates), policies (free cancellation, no prepayment, child/pet stays), price, rating and review summary, photos, and the list of available room suites for the requested window. Use to enrich property listings with real-time availability and pricing, monitor a specific competitor hotel over time, validate amenities and photos before displaying venue details to end users, or fetch full details after discovering the property URL via the Booking Search endpoint.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Full Booking.com URL of the property page. Only `booking.com` and `www.booking.com` hosts are accepted.
`rooms`	Yes	Number of rooms to book.
`adults`	Yes	Number of adult guests across all rooms.
`children`	Yes	Number of child guests across all rooms (0–10). Pass `0` if there are no children.
`currency`	No	Currency of the prices returned in the response. Use `hotelCurrency` to keep each property's native currency. Provide one exact documented value (52 allowed), e.g. `hotelCurrency`, `usd`.
`language`	No	Language of the Booking.com interface and localized fields in the response.
`checkInDate`	Yes	Check-in date in `YYYY-MM-DD` format. Must be in the future and earlier than `checkOutDate`.
`checkOutDate`	Yes	Check-out date in `YYYY-MM-DD` format. Must be later than `checkInDate`.
`childrenAges`	No	Comma-separated list of child ages, one entry per child (each `0`–`17`). Required when `children > 0` and the number of ages must equal `children`. Example: `1,3,7`

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 24, 2026

changedInput schema / properties / currency / description

Previous value: -"Currency of the prices returned in the response. Use `hotelCurrency` to keep each property's native currency."New value: +"Currency of the prices returned in the response. Use `hotelCurrency` to keep each property's native currency. Provide one exact documented value (52 allowed), e.g. `hotelCurrency`, `usd`."

removedInput schema / properties / currency / enum

Removed value: -[
-  "hotelCurrency",
-  "usd",
-  "eur",
-  "aed",
-  "ars",
-  "aud",
-  "azn",
-  "bhd",
-  "brl",
-  "cad",
-  "chf",
-  "clp",
-  "cny",
-  "cop",
-  "czk",
-  "dkk",
-  "egp",
-  "fjd",
-  "gbp",
-  "gel",
-  "hkd",
-  "huf",
-  "idr",
-  "ils",
-  "inr",
-  "isk",
-  "jod",
-  "jpy",
-  "krw",
-  "kwd",
-  "kzt",
-  "mdl",
-  "mop",
-  "mxn",
-  "myr",
-  "nad",
-  "nok",
-  "nzd",
-  "omr",
-  "pln",
-  "qar",
-  "ron",
-  "rub",
-  "sar",
-  "sek",
-  "sgd",
-  "thb",
-  "try",
-  "twd",
-  "uah",
-  "xof",
-  "zar"
-]

Changed2 schema fields changedJul 8, 2026

addedInput schema / properties / childrenAges

Added value: +{
+  "description": "Comma-separated list of child ages, one entry per child (each `0`–`17`). Required when `children > 0` and the number of ages must equal `children`.\n\nExample: `1,3,7`\n",
+  "type": "string"
+}

removedInput schema / properties / childrenAgesJson

Removed value: -{
-  "description": "JSON-encoded array of child ages, one entry per child (each `0`–`17`). Required when `children > 0` and the array length must equal `children`. Must not be passed when `children = 0`.\n\nExample: `[1, 3, 7]`\n",
-  "type": "string"
-}

AddedMay 13, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds real value by enumerating what is returned (identity, policies, price, rating, photos, room suites) and noting prices/availability are real-time, though it says nothing about auth, rate limits, or error cases.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening line 'Get Booking Hotel Details' merely restates the title and is wasted space. The remainder is a dense but informative sentence followed by a use-case list; it is not bloated, but the redundant lead-in and heavy enumeration keep it from being tightly front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining return values, and it does so thoroughly (identity, policies, price, rating, photos, room suites). For a read-only detail endpoint it is essentially complete, missing only error/failure behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter is already documented in the schema. The description restates the stay-date and guest-composition inputs but adds no syntax, format, or constraint detail beyond what the schema already provides, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (fetches) and resource (a single Booking.com property by full URL), and explicitly distinguishes itself from the sibling search endpoint by describing this as the 'fetch full details after discovering the property URL via the Booking Search endpoint' step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives four concrete use cases (enrich listings, monitor a competitor, validate amenities/photos, fetch details after search) and names the discovery-then-detail workflow with the sibling tool. It lacks explicit when-not-to-use exclusions, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HasData tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?