Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

booking_flights_search

Search flights on Booking.com and return normalized round-trip or one-way offers between two locations. Use origin, destination, departure date, and optional return date.

Instructions

Search Booking.com flights. Returns normalized round-trip or one-way flight offers between two Booking.com flight-search locations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesDestination location id, same composite format as from
fromYesOrigin location id, e.g. SGN.AIRPORT, from a prior autocomplete result
sortNoResult sort order, default BEST
typeNoTrip type, default ROUNDTRIP
adultsNoNumber of adults, 1-9, default 1
departYesDeparture date, YYYY-MM-DD
returnNoReturn date, YYYY-MM-DD, required when type is ROUNDTRIP
childrenNoNumber of children, 0-9
to_countryNoDestination country code
cabin_classNoCabin class, default ECONOMY
from_countryNoOrigin country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "ROUNDTRIP",
+  "ONEWAY"
+]
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It usefully adds that results are 'normalized' and limited to round-trip or one-way offers between two locations. However, it does not mention sorting defaults, date format requirements beyond the schema, or the read-only nature of the search in explicit terms.

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

Conciseness5/5

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

The description is two short sentences with the key action and result type front-loaded. No redundant phrasing or filler.

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?

For a tool with 11 parameters and no output schema or annotations, the description is somewhat thin: it identifies the resource and result type but gives no orientation on constructing a valid request (e.g., resolving location IDs via autocomplete) or what a 'normalized offer' contains. The rich parameter descriptions compensate partially, but overall context is adequate rather than complete.

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 echoes the from/to and type parameters ('between two... locations', 'round-trip or one-way') but adds no meaning beyond the schema; it does not explain the location ID composite format or required return date for round-trip searches beyond what the schema already states.

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?

The description opens with a specific action ('Search Booking.com flights') and names the resource and result type ('normalized round-trip or one-way flight offers'), which clearly distinguishes it from sibling tools like booking_attractions_search and expedia_flights_search. It also states the scope: between two Booking.com flight-search locations.

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?

No guidance is given about when to use this tool over alternatives. The description does not mention that expedia_flights_search or agoda_flights_search exist for other providers, nor does it point to booking_flights_autocomplete for resolving location IDs before calling search. The agent has to infer usage from the name and schema.

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