Skip to main content
Glama

Searchapi

by io.searchapi
OverviewDiscussionsAdmin

Google Flights One Way

google_flights_one_way
Read-only

Search one-way Google Flights with airline, time, price, and booking details.

Required on every call, including token follow-ups: departure_id, arrival_id, outbound_date. Preserve all original search options, including travel_class, passenger counts, currency, and filters.

Workflow:

  1. Search for flight options.

  2. Repeat the arguments with the chosen flight's booking_token to retrieve booking details.

Round-trip: google_flights_round_trip. Flexible dates: google_flights_calendar_one_way.

Input Schema

NameRequiredDescriptionDefault
glNoISO 3166-1 alpha-2 country code in lowercase (e.g., 'us', 'gb', 'de'). Affects pricing and flight availability. Default: us.
stopsNoMaximum stops filter: nonstop (direct only), one_stop_or_fewer (at most 1 stop), two_stops_or_fewer (at most 2 stops), any (no limit). Use the named value (e.g. 'two_stops_or_fewer'), not a bare number like '2'. Default: any.
adultsNoNumber of adults (1-9). Default: 1.
sort_byNoSort order. Default: top_flights.
childrenNoNumber of children (0-9). Default: 0.
currencyNoCurrency code (ISO 4217, e.g., 'USD', 'EUR', 'GBP'). Default: USD.
max_priceNoMaximum price filter. Flights above this price (in the specified currency) are excluded.
arrival_idYesIATA airport code (e.g., 'LAX') or kgmid (e.g., '/m/030qb3t' for Los Angeles). City names must first be converted using google_flights_location_search.
checked_bagsNoNumber of checked bags (0-9). Shows prices with checked bag fees included. Cannot exceed total passenger count.
departure_idYesIATA airport code (e.g., 'JFK') or kgmid (e.g., '/m/02_286' for New York). City names must first be converted using google_flights_location_search.
travel_classNoTravel class: economy, premium_economy, business, first_class. Default: economy.
booking_tokenNoToken from the selected flight for retrieving booking details.
carry_on_bagsNoNumber of carry-on bags (0-9). Shows prices with carry-on fees included for budget airlines. Cannot exceed total passenger count.
outbound_dateYesDeparture date in YYYY-MM-DD format (ISO 8601). Required.
infants_on_lapNoNumber of infants on lap (0-9). Default: 0. A value above 0 may result in longer request processing times.
infants_in_seatNoNumber of infants in seat (0-9). Default: 0. A value above 0 may result in longer request processing times.
excluded_airlinesNoComma-separated IATA airline codes to exclude (e.g., 'NK,F9').
included_airlinesNoComma-separated IATA airline codes to include (e.g., 'AA,UA,DL').
max_flight_durationNoMaximum total flight duration in minutes (e.g., 600 for 10 hours). Excludes flights exceeding this duration.
exclude_basic_economyNoSet to true to exclude Basic Economy fares, the cheapest and most restrictive ones. Only valid with travel_class economy. Google Flights offers this filter for flights within the US, its territories and Canada; on other routes results are unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / infants_in_seat / description
      Previous value: -"Number of infants in seat (0-9). Default: 0."New value: +"Number of infants in seat (0-9). Default: 0. A value above 0 may result in longer request processing times."
    • changedInput schema / properties / infants_on_lap / description
      Previous value: -"Number of infants on lap (0-9). Default: 0."New value: +"Number of infants on lap (0-9). Default: 0. A value above 0 may result in longer request processing times."
  2. Changed1 schema field changed
    • addedInput schema / properties / exclude_basic_economy
      Added value: +{
+  "description": "Set to true to exclude Basic Economy fares, the cheapest and most restrictive ones. Only valid with travel_class economy. Google Flights offers this filter for flights within the US, its territories and Canada; on other routes results are unchanged.",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / booking_token / description
      Previous value: -"Token for retrieving booking details for a selected flight. Found in the booking_token field of flight results."New value: +"Token from the selected flight for retrieving booking details."
  4. Changed2 schema fields changed
    • changedInput schema / properties / stops / description
      Previous value: -"Maximum stops filter. Default: any."New value: +"Maximum stops filter: nonstop (direct only), one_stop_or_fewer (at most 1 stop), two_stops_or_fewer (at most 2 stops), any (no limit). Use the named value (e.g. 'two_stops_or_fewer'), not a bare number like '2'. Default: any."
    • changedInput schema / properties / travel_class / description
      Previous value: -"Travel class. Default: economy."New value: +"Travel class: economy, premium_economy, business, first_class. Default: economy."
  5. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  6. Changed1 schema field changed
    • changedInput schema / properties / gl / description
      Previous value: -"Country code (ISO 3166-1 alpha-2, e.g., 'us', 'gb', 'de'). Affects pricing and flight availability. Default: us."New value: +"ISO 3166-1 alpha-2 country code in lowercase (e.g., 'us', 'gb', 'de'). Affects pricing and flight availability. Default: us."
  7. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds valuable behavior beyond those annotations: the booking_token follow-up workflow, the requirement to preserve original search options, and the need to repeat required parameters on follow-up calls. It does not describe response format or pagination, but it is substantially more informative than the annotations 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 front-loaded with the core purpose, then moves through required parameters, workflow, and sibling alternatives. Every sentence carries actionable information, and the bullet structure makes the two-step workflow easy to scan.

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?

For a 20-parameter search tool with full schema coverage, rich annotations, and no output schema, the description supplies the essential missing context: workflow, required-parameter persistence, token follow-up behavior, and alternative-tool routing. Return intent is indicated through 'flight options' and 'booking details', which is sufficient here.

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 description coverage is 100%, so the baseline is 3. The description adds semantic guidance beyond the schema by explaining that departure_id, arrival_id, and outbound_date are required even on token follow-ups and that all original search options should be preserved when retrieving booking details.

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 one-way Google Flights', and it distinguishes the tool from round-trip and flexible-date siblings by naming them. An agent can identify the tool's scope without opening the schema.

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?

It gives a clear two-step workflow, states required parameters on every call including token follow-ups, and explicitly routes round-trip searches to google_flights_round_trip and flexible-date searches to google_flights_calendar_one_way. This tells the agent when to use this tool versus the main alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Searchapi toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources