flights-mcp

Search Flights

search_flights

Read-only

Search live Google Flights for one-way or round-trip itineraries with configurable filters, then get booking links and price totals.

Instructions

Search Google Flights for one-way or round-trip flights.

Omit return_date for a one-way search. Prices are totals for all passengers in the requested currency. Results are live scrapes of Google Flights and may change between calls, so treat them as indicative and share the returned google_flights_url for booking.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`seat`	No	Cabin class.	economy
`adults`	No	Adult passengers.
`sort_by`	No	How to order the returned itineraries.	price
`airlines`	No	Restrict to these airline IATA codes (e.g. ['SK', 'LH']) or alliances ('ONEWORLD', 'SKYTEAM', 'STAR_ALLIANCE').
`children`	No	Children aged 2-11.
`currency`	No	Currency for prices. Empty lets Google decide.
`language`	No	Language for names. Empty lets Google decide.
`max_price`	No	Maximum total price, in the requested currency.
`max_stops`	No	Maximum stops per leg. Use 0 for non-stop only.
`to_airport`	Yes	Destination IATA airport code, e.g. 'JFK'.
`max_results`	No	Maximum itineraries to return.
`return_date`	No	Return date in 'YYYY-MM-DD' format. Omit for a one-way search; providing it makes the search a round-trip.
`checked_bags`	No	Checked bags to include in the price estimate.
`from_airport`	Yes	Origin IATA airport code, e.g. 'OSL'.
`carry_on_bags`	No	Carry-on bags to include in the price estimate.
`departure_date`	Yes	Outbound date in 'YYYY-MM-DD' format.
`infants_on_lap`	No	Infants on a lap. Requires one adult each.
`infants_in_seat`	No	Infants occupying their own seat.
`exclude_basic_economy`	No	Exclude basic economy fares.
`hide_separate_and_self_transfer`	No	Hide separate-ticket and self-transfer itineraries.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Number of itineraries in this response.
`currency`	No
`truncated`	No	True when more itineraries were available than were returned.
`itineraries`	No
`cheapest_price`	No	Lowest price among the returned itineraries.
`google_flights_url`	Yes	Google Flights URL reproducing this exact search.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Sep 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that results are 'live scrapes of Google Flights' that 'may change between calls,' advises treating them as indicative, and directs users to the returned google_flights_url for booking. This adds meaningful behavioral context not available from annotations or schema alone.

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 four concise sentences with no filler. The purpose is front-loaded, and operational caveats about return_date, pricing, and result volatility are packed into a compact, readable structure.

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

Completeness5/5

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

Despite having 20 parameters, the schema covers all parameter semantics, an output schema exists, and annotations declare read-only/open-world behavior. The description adds the critical operational caveats—live data, indicative results, and booking via the returned URL—making the complete picture sufficient for safe invocation.

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 coverage is 100%, so the baseline is 3. The description adds useful semantic context beyond the schema by clarifying that 'Prices are totals for all passengers in the requested currency,' which affects interpretation of currency, max_price, and passenger-count parameters. It also restates the return_date one-way/round-trip behavior.

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 uses a specific verb and resource: 'Search Google Flights for one-way or round-trip flights.' It clearly defines the tool's function and scope, and there are no sibling tools that could create ambiguity.

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?

The description gives clear usage context for the main variant: 'Omit return_date for a one-way search.' It also explains that prices are totals for all passengers and that results are indicative. Since there are no sibling tools, exclusions or alternatives aren't applicable; this is clear context without full when-not 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

search_flightsA