Skip to main content
Glama
HaroldLeo

Google Flights MCP Server

by HaroldLeo

search_round_trip_flights

Find round-trip flight options between specified airports for exact departure and return dates, with options to filter by price, stops, and passenger details.

Instructions

Fetches available round-trip flights for specific departure and return dates.
Can optionally return only the cheapest flight found.

💡 TIP: Default max_stops=2 provides more reliable scraping. For direct flights only,
use search_direct_flights() with is_round_trip=True instead.

Args:
    origin: Origin airport code (e.g., "DEN").
    destination: Destination airport code (e.g., "LAX").
    departure_date: The specific departure date (YYYY-MM-DD format).
    return_date: The specific return date (YYYY-MM-DD format).
    adults: Number of adult passengers (default: 1).
    children: Number of children (2-11 years, default: 0).
    infants_in_seat: Number of infants in seat (under 2 years, default: 0).
    infants_on_lap: Number of infants on lap (under 2 years, default: 0).
    seat_type: Fare class - economy/premium_economy/business/first (default: "economy").
    max_stops: Maximum number of stops (0=direct, 1=one stop, 2=two stops, default: 2).
               Lower values = more reliable scraping. Set higher if needed, but may reduce reliability.
    return_cheapest_only: If True, returns only the cheapest flight (default: False).

Example Args:
    {"origin": "DEN", "destination": "LAX", "departure_date": "2025-08-01", "return_date": "2025-08-08"}
    {"origin": "DEN", "destination": "LAX", "departure_date": "2025-08-01", "return_date": "2025-08-08", "adults": 2, "children": 2}
    {"origin": "DEN", "destination": "LAX", "departure_date": "2025-08-01", "return_date": "2025-08-08", "max_stops": 0}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originYes
destinationYes
departure_dateYes
return_dateYes
adultsNo
childrenNo
infants_in_seatNo
infants_on_lapNo
seat_typeNoeconomy
max_stopsNo
return_cheapest_onlyNo
max_resultsNo
compact_modeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing important behavioral traits: it mentions scraping reliability implications of max_stops values, explains the return_cheapest_only option, and provides practical usage tips. However, it doesn't cover rate limits, authentication needs, or error conditions that would be valuable for a flight 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.

Conciseness5/5

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

The description is efficiently structured with purpose statement upfront, usage tip, parameter explanations, and examples. Every sentence adds value with no redundancy. The bullet-point style for parameters and clear sectioning makes it easy to parse while maintaining comprehensive coverage.

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 complex 13-parameter tool with no annotations but with an output schema, the description provides excellent coverage of inputs, usage context, and sibling tool relationships. It explains all parameters thoroughly and gives practical guidance. The presence of an output schema reduces the need to describe return values, making this nearly complete for agent usage.

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?

Given 0% schema description coverage, the description compensates well by explaining all 13 parameters with clear semantics, examples, and defaults. It adds meaningful context beyond schema titles, such as age ranges for children/infants, fare class options for seat_type, and reliability implications for max_stops. The example args provide concrete usage patterns.

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 clearly states the tool's purpose with specific verbs ('fetches available round-trip flights') and distinguishes it from sibling tools by mentioning 'search_direct_flights()' as an alternative for direct flights. It explicitly identifies the resource (flights) and scope (round-trip with specific dates).

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?

The description provides explicit guidance on when to use this tool versus alternatives, stating 'For direct flights only, use search_direct_flights() with is_round_trip=True instead.' It also offers a tip about max_stops defaults and reliability implications, giving clear context for decision-making.

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

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