Skip to main content
Glama

booking_search

Search for hotels and properties on Booking.com with optional amenity filters (pets, parking, pool) to find matching accommodations with ratings, prices, and availability.

Instructions

Search for hotels and properties on Booking.com. Returns property names, ratings, prices, and availability indicators. Optionally filter server-side by amenities/facilities (e.g. pets, parking, pool) so only matching properties are returned.\n\nPRICE FIELDS: pricePerNight and totalPrice both carry the same numeric value extracted from the card. On multi-night searches this is typically the TOTAL stay price (not per-night). Check priceIsTotal (true = total, false = explicitly per-night) and priceNote (raw card text) for context. currency is auto-detected from the card text when visible (e.g. 'CHF', 'EUR', 'USD'). For accurate per-night pricing on multi-night stays, divide totalPrice by number of nights.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomsNoNumber of rooms (default: 1)
adultsNoNumber of adults (default: 2)
checkInYesCheck-in date in YYYY-MM-DD format
rawNfltNoAdvanced/escape hatch: raw Booking.com `nflt` filter chips, ';'-delimited (e.g. 'hotelfacility=4;popular_activities=2'). Merged with `amenities`. Use when an amenity code needs correcting or for filters not in the amenities list.
checkOutYesCheck-out date in YYYY-MM-DD format
childrenNoNumber of children (default: 0)
amenitiesNoFilter results server-side to properties offering ALL of these amenities/facilities. Supported: pets, parking, pool, restaurant, room_service, front_desk_24h, fitness, non_smoking, airport_shuttle, family_rooms, ev_charging, spa, hot_tub, sauna, free_wifi, air_conditioning. Example: ["pets", "parking", "pool"] for pet-friendly hotels with parking and a pool.
maxResultsNoMaximum results to return (default: 10, max: 50)
destinationYesDestination to search (e.g. 'Paris', 'New York', 'Rome, Italy')
flex_windowNoDate flexibility window (days). 0 = exact dates only (default). Positive values search with flexible dates around the given checkIn/checkOut: 1=±1 day, 2=±2 days, 3=±3 days, 7=±7 days. When >0, Booking.com returns properties available across the date window, which can reveal cheaper options just outside your exact dates.
Behavior4/5

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

Given no annotations, the description carries full burden. It explains price fields ambiguity (pricePerNight vs totalPrice), priceIsTotal flag, currency detection, and server-side filtering. However, it misses details on pagination, error handling, and rate limits.

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

Conciseness4/5

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

The description is front-loaded with the primary purpose and well-structured with a dedicated 'PRICE FIELDS' section. While somewhat lengthy, each sentence contributes meaning, making it efficient.

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

Completeness3/5

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

With 10 parameters and no output schema, the description covers search, filtering, flexibility, and price nuances. However, it lacks details about pagination, default sorting, or whether only available properties are returned, leaving some gaps.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining price field relationships, flex_window behavior, and rawNflt usage, which go beyond the schema descriptions.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Search for hotels and properties on Booking.com' and lists what it returns. It distinguishes from siblings by focusing on the initial search with filtering, but does not explicitly compare to related tools like booking_check_availability or booking_get_prices.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternatives like booking_check_availability or booking_filter_results. It implies usage for general search but lacks explicit when-not or alternative recommendations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/markswendsen-code/mcp-booking'

If you have feedback or need assistance with the MCP directory API, please join our Discord server