Skip to main content
Glama
Google Flights Fares MCP Server

Google Flights Fares MCP Server

Get Google Flights fares

get_google_flights_fares
Read-onlyIdempotent

Search Google Flights by route and travel dates to retrieve fare options with prices, airlines, flight numbers, times, duration, stops, layovers, and emissions.

Instructions

Search Google Flights for a route and dates. Returns one row per flight option with price, airlines, flight numbers, departure and arrival times, duration, stops, layovers, and emissions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_google_flights_fares"
  }
}

Input Schema

NameRequiredDescriptionDefault
cabinNoeconomy (default), business, or first. Premium economy is not supported.
adultsNoAdult passengers, 1 to 9. Default 1. price_total is for all passengers; price_per_adult divides it.
dedupeNotrue (default): an option already returned for the same route and dates in this run is skipped and not charged.
routesNoOne route per line, origin to destination, for example JFK to LAX, JFK-LAX, or New York to London. Airport codes (3 capital letters) give exact airports; a city name lets Google pick the city's airports. From Clay, put the column inside a one item list.
currencyNoISO currency code for the prices, for example USD, EUR, GBP. Default USD.
trip_daysNoRound trip only: days between departure and return, 1 to 60. Default 7. Ignored when return_date is set.
trip_typeNoround_trip (default) or one_way. A round trip price is the round trip total, and the row lists the outbound flights.
return_dateNoOptional. YYYY-MM-DD. Works with one departure date only; for several dates use trip_days.
nonstop_onlyNotrue: keep only nonstop options; others are left out and not charged. Default false.
max_charge_usdNoOptional. The run stops before a charge that would pass this amount. Summary rows are always returned.
departure_datesNoOne or more outbound dates, YYYY-MM-DD, up to 330 days ahead. Each date is its own search. Empty: 21 days from today.
max_flights_per_searchNo1 to 100. Default 30. The actor reads the flight list Google renders on the search page, usually 6 to 35 options.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, open-world, idempotent, non-destructive behavior. The description adds useful output-shape context by enumerating returned fields, but it does not disclose charging, dedupe behavior, rate limits, or other caveats beyond annotations.

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?

Two short, front-loaded sentences with no redundant restatement of the name or schema. Every sentence contributes purpose or return shape.

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?

The tool is complex with 12 parameters, but the schema is fully documented and annotations cover its safety profile. With no output schema, enumerating returned fields is valuable; the only notable gap is explicit usage guidance.

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%, documenting all 12 parameters including defaults, ranges, and enum meanings. The description adds no parameter-level meaning beyond the schema, so the baseline applies.

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 (Search) and resource (Google Flights), scoped to a route and dates. Even without siblings it is unambiguous what the tool does.

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?

Offers no explicit when-to-use, when-not-to-use, prerequisites, or alternative routing; the closest is the purpose sentence itself. With no sibling tools alternatives are not an issue, but usage selection remains implicit.

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