Skip to main content
Glama
manganate006

google-flights-mcp

by manganate006

search_flights

Find the best airfare deals on Google Flights by specifying departure and destination airports, dates, travelers, seat class, and stop preferences.

Instructions

Search Google Flights for the best prices.
Tries multiple departure airports (default: Nice NCE, Marseille MRS).

All airports must be IATA codes. If you only know a city name, call find_airport
(or find_airports_near) first to resolve it.

Args:
    to_airport: IATA destination code(s), comma-separated for multi-airport cities (e.g. "BCN" or "LHR,LGW,STN")
    departure_date: Departure date YYYY-MM-DD
    return_date: Return date YYYY-MM-DD (empty for one-way)
    from_airports: Comma-separated IATA departure codes (default: NCE,MRS)
    adults: Number of adults (default 2)
    children: Number of children (default 2)
    infants_in_seat: Infants with seat (default 0)
    infants_on_lap: Infants on lap (default 0)
    seat: Seat class: economy, premium-economy, business, first
    max_stops: Max stops: -1 = no limit (default), 0 = direct only, 1 = max one stop
    airlines: Comma-separated IATA airline codes to restrict to (e.g. "AF,U2"); empty = all
    currency: ISO currency code (default EUR)
    language: Language code (default fr)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seatNoeconomy
adultsNo
airlinesNo
childrenNo
currencyNoEUR
languageNofr
max_stopsNo
to_airportYes
return_dateNo
from_airportsNo
departure_dateYes
infants_on_lapNo
infants_in_seatNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses that it tries multiple departure airports by default, accepts IATA codes, and details all parameters. No annotations exist, so description carries full burden. Could mention output structure or pricing limitations, but current coverage is strong.

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?

Well-structured with summary, prerequisite note, and bullet-style Args list. Slightly verbose due to 13 parameters, but each line adds value. No wasted sentences.

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?

Covers 13 parameters with defaults, 2 required ones marked, IATA code resolution guidance, and output schema exists to handle return values. Complete for an AI agent to use correctly.

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

Parameters5/5

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

Schema coverage is 0%, but the description defines every parameter with data types, defaults, and usage examples (e.g., 'YYYY-MM-DD', comma-separated IATA codes). Adds critical meaning beyond the schema alone.

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 'Search Google Flights for the best prices' with specific verb and resource. Clearly distinguishes from sibling tools (e.g., search_multi_city, search_flexible_dates) by focusing on simple round-trip/one-way search with multiple departure airports.

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

Usage Guidelines5/5

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

Explicitly instructs to call find_airport or find_airports_near if only city names are known. Provides default behavior and parameter format guidance. No mention of when not to use, but context about alternatives is sufficient.

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/manganate006/google-flights-mcp'

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