Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

booking_search

Search Booking.com hotels by destination and check-in/check-out dates, returning prices, ratings, and distance with optional guest and room filters.

Instructions

Search Booking.com hotels. Searches Booking.com hotels for a destination query between checkin and checkout (YYYY-MM-DD, both required). adults is 1 to 9 (default 2), rooms 1 to 8 (default 1), children 0 to 9, and page is 1-based. Each property has name, price, currency, review_score, star_rating and distance; results_count gives the total.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based result page, default 1
queryYesDestination name or city
roomsNoNumber of rooms, 1-8, default 1
adultsNoNumber of adults, 1-9, default 2
checkinYesCheck-in date, YYYY-MM-DD
checkoutYesCheck-out date, YYYY-MM-DD
childrenNoNumber of children, 0-9

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It helpfully discloses parameter defaults and ranges plus the returned property fields and total count, but it does not cover read-only nature explicitly, pagination limits, rate limits, authentication, or result ordering. Useful but incomplete for a search tool.

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?

Front-loaded with purpose, then parameter details, then return fields. Efficient overall, though some parameter ranges/defaults duplicate the schema and could be trimmed. Every sentence has some value, especially the return-field sentence since there is no output schema.

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?

For a 7-parameter search tool with no annotations and no output schema, the description covers purpose, required dates, parameter bounds, and return fields. It is missing usage alternatives and behavioral details like pagination behavior, but the core information an agent needs to call it correctly is present.

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 the baseline is 3. The description repeats ranges and defaults already documented in the schema (e.g., adults 1-9 default 2, page 1-based) without adding new semantic meaning beyond what the schema provides.

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 and resource ("Search Booking.com hotels") and scopes it to a destination query with date range, which clearly separates it from sibling detail tools like booking_hotel_detail and other hotel search tools like agoda_hotels_search. An agent can identify the tool without opening the schema.

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

Usage Guidelines3/5

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

The description implies when to use the tool by naming the destination query and date range, but never states explicit alternatives or exclusions (e.g., when to use booking_hotel_detail or agoda_hotels_search instead). This is implied usage rather than actionable routing guidance.

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

Deploy Server

Other Tools