Skip to main content
Glama

Google Flights Search (Real-Time Fares)

by com.flightpowers
OverviewAdmin

Server Details

Real-time Google Flights fares for agents. Three things people do with this server. Scan for deals: one call takes a date range and a list of destination airports, expands every combination server side, and returns each fare with Google's own low, typical or high verdict. Put live search in your app: flat JSON with a bookable link on every result, and round trips priced as paired legs. Run a 24/7 AI travel agent: add the server, sign in with Google, and schedule it. No ads, no sponsored content. You bring your own RapidAPI key, so every search is billed to your plan and never to anyone else's. Add https://flights.flightpowers.com/mcp , click Sign in, sign in with Google, and paste your RapidAPI key once on the page that opens. Scripts and clients without a sign-in button send the key as x-rapidapi-key on the same URL.

Ownership verified
Status
Healthy
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL
Repository
mtnrabi/google-flights-mcp
GitHub Stars
1
Server Listing
google-flights-mcp

TDQS

A4.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are cleanly split by trip type: one-way versus round-trip. An agent can select the correct one from the query's return-trip requirement without any overlap.

Naming Consistency5/5

Both tools follow the same search_<trip_type>_flights pattern using snake_case. The naming is predictable and signals the key distinction immediately.

Tool Count4/5

Two tools is minimal, but they map directly to the two core fare-search modes and each supports flexible dates and multiple destinations. No redundant tools exist, though the set is slightly below the typical 3-15 range.

Completeness4/5

The tool surface covers one-way and round-trip fare searches with flexible dates, multi-destination input, and price insights. Multi-city itineraries are not explicitly supported, which is a minor gap for a Google Flights search server.

Available Tools

2 tools
search_oneway_flightsFlightPowers: search one-way flightsA
Read-only
Inspect

FlightPowers one-way fare search: live prices read from Google Flights. Input: origin and destination IATA codes -- the destination may be several codes, as "BCN,LIS,ATH" or ["BCN","LIS","ATH"] -- plus either one departure date or a date range. Returns each flight's price, airline, duration, stops, a bookable buy_link, and Google's historical price range (price_insights_low / price_insights_high) so you can say whether a fare is actually a good deal.

Use it for any one-way fare question, including open-ended ones. For a flexible search make ONE call with a date range and/or several destinations -- do NOT call it once per date. 'Cheapest flight to Sri Lanka anywhere in October' is one call, not thirty.

Each date/destination combination is one billed request; the count and the plan's remaining quota come back in api_usage.

by_destination carries one entry per destination you asked for -- empty ones included, each with a reason -- so read it before telling a user a destination has no flights.

Requires the caller's own RapidAPI key for the Google Flights Live API. Get one (free tier available) at https://rapidapi.com/mtnrabi/api/google-flights-live-api, then pass it as an x-rapidapi-key header (preferred), a ?rapidapi_key= query parameter on the server URL, or your client's own API key field -- first non-empty wins. Usage counts against the caller's own RapidAPI plan, not ours; every response reports what it spent and what is left in api_usage.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum flights to return, after merging and sorting.
sort_byNo"best", "price", or "duration". Applied across all results.best
currencyNoISO currency code, default "usd".usd
max_priceNoOnly return flights at or below this price.
max_stopsNoMaximum stops per flight. 0 means non-stop only.
seat_typeNo1 economy, 2 premium economy, 3 business, 4 first.
passengersNoPassenger counts as [adults, children, infants].
to_airportYesDestination airport. One IATA code ("BCN"), several separated by commas ("BCN,LIS,ATH"), or a list (["BCN","LIS","ATH"]) -- every shape is accepted and the destinations are compared in the same search.
from_airportYesOrigin IATA code, e.g. "TLV". One origin per search; a second one is refused rather than searched.
max_searchesNoCap the billed requests this call may make. Lower it to spend less of the plan's quota on a wide search; the range is then sampled evenly rather than cut short.
use_fallbackNoLeave unset. Switches the search to a second, independent flight data source instead of the usual Google Flights page read. Unset already escalates to that source once, automatically, after a search's retries have failed. true forces it inline on every attempt -- much slower, and it can time out. false disables it entirely, that automatic retry included.
airline_codesNoRestrict to these airline codes, e.g. ["LY"].
departure_dateNoSingle departure date, "YYYY-MM-DD".
arrival_time_maxNoLatest arrival hour, 0-23.
arrival_time_minNoEarliest arrival hour, 0-23.
departure_date_toNoLast date of a departure range.
departure_time_maxNoLatest departure hour, 0-23.
departure_time_minNoEarliest departure hour, 0-23.
departure_date_fromNoFirst date of a departure range.
exclude_airline_codesNoExclude these airline codes.

Output Schema

ParametersJSON Schema
NameRequiredDescription
messageNoPresent when there is something the model must relay to the user rather than silently absorb -- no results, a degraded search, a missing key or a spent quota.
partialNoPresent when some searches failed but others succeeded. Plain text saying how much of the request the results cover.
resultsYesThe itineraries or properties found, already sorted and deduplicated. An empty array is only meaningful when search_status is 'empty'.
api_usageNoWhat this call cost the caller's own RapidAPI plan, and what remains on it. Present on every response that reached the upstream, including a degraded one -- a search that failed was still billed.
signup_urlNoWhere the caller subscribes or changes plan.
result_countNo
needs_api_keyNoTrue when no usable RapidAPI key arrived with the call, or the upstream rejected the one that did. No search was run and nothing was billed; signup_url and message say how to fix it.
search_statusNoWhether the underlying search actually completed, read from the backend's X-Search-Status header. 'ok': every combination searched returned results. 'empty': the search completed and Google genuinely has no itineraries for it -- a real answer, not a failure. 'partial': some combinations returned results and some failed, so the list is incomplete. 'degraded': every combination failed, so the search did not happen and an empty list means nothing; this case is also flagged with isError: true and is safe to retry.
by_destinationNoOne entry per destination the REQUEST asked for, in request order, present whether or not that destination has any flights in `results`. A destination with an empty `rows` array is a hole in the answer, and `reason` says which kind of hole: 'no_flights' (searched, answered, Google has nothing), 'search_failed' (searched and the search errored, so nothing is known), 'not_in_limit' (searched, found flights, none fitted in `limit`) or 'not_searched' (never searched -- the per-call fan-out cap sampled it away). 'ok' means it has rows. Read this rather than inferring coverage from `results`: a destination missing from `results` looks identical to one that has no flights, and they are not the same answer. `rows` are the same row objects that are in `results`, in the same order -- nothing here is data the answer does not already contain.
quota_exhaustedNoTrue when the caller's RapidAPI plan has no requests left for the current period.
search_coverageNoWhat was actually searched. Present whether or not the request was truncated, so a model can state honestly what its answer rests on.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations carry only the basic safety profile (readOnly=true, non-destructive, open-world, non-idempotent). The description adds substantial operational behavior beyond them: each date/destination combination is one billed request against the caller's own RapidAPI quota, api_usage reports spending and remaining quota, by_destination includes empty entries with a reason so the agent must read it before claiming a destination has no flights, and auth requires the caller's own key with a documented precedence order. This far exceeds annotation coverage with genuinely useful context.

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?

Purpose is front-loaded in the first clause, and each paragraph earns its place: returns, batching guidance, billing model, by_destination caveat, auth. The RapidAPI paragraph is the longest but is operationally necessary since the tool cannot be called without a caller-provided key. Zero filler, though the auth section could have been tightened slightly.

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 tool with billing and auth dependencies, everything operational is covered: return contents (backed by an output schema), correct call batching, quota accounting, empty-result handling, and key provisioning. The only unspoken item is the explicit round-trip alternative, and with the sibling named in the title and the 'one-way' scope stated twice, that gap is negligible.

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, but the description adds real cross-parameter meaning: the multi-shaped to_airport inputs are compared in the same search, departure_date_from/to form a single search span rather than per-date calls, max_searches caps billed requests with even sampling rather than truncation, use_fallback's escalation behavior is explained, and auth key precedence is specified. It complements the schema rather than repeating it.

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?

Opens with 'FlightPowers one-way fare search: live prices read from Google Flights' — a specific verb, resource, and data source in the first clause. The 'one-way' scope cleanly distinguishes it from the lone sibling search_roundtrip_flights, and the description enumerates the returned fields (price, airline, duration, stops, buy_link, price insights) so the agent knows exactly what it produces.

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?

States 'Use it for any one-way fare question, including open-ended ones' and gives explicit batching instruction: 'make ONE call with a date range and/or several destinations — do NOT call it once per date,' with a concrete example ('Cheapest flight to Sri Lanka anywhere in October' is one call, not thirty). It stops just short of explicitly naming search_roundtrip_flights for round-trip queries, though the 'one-way fare question' phrasing implies that exclusion.

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

search_roundtrip_flightsFlightPowers: search round-trip flightsA
Read-only
Inspect

FlightPowers round-trip fare search: live prices read from Google Flights, priced as paired legs rather than two separate one-ways. Input: origin and destination IATA codes -- the destination may be several codes, as "BCN,LIS,ATH" or ["BCN","LIS","ATH"] -- a departure date or range, and either a return date or a trip length in nights. Returns the total price for both legs, per-leg airline, stops and duration, and a single bookable buy_link for the trip.

Use it for any return-trip fare question. For a flexible search make ONE call: pass departure_date_from / departure_date_to for the outbound range and nights instead of return_date to compare trip lengths -- '5 to 7 nights in Rome sometime in May' is one call.

Each date/destination combination is one billed request; the count and the plan's remaining quota come back in api_usage.

by_destination carries one entry per destination you asked for -- empty ones included, each with a reason -- so read it before telling a user a destination has no flights.

Requires the caller's own RapidAPI key for the Google Flights Live API. Get one (free tier available) at https://rapidapi.com/mtnrabi/api/google-flights-live-api, then pass it as an x-rapidapi-key header (preferred), a ?rapidapi_key= query parameter on the server URL, or your client's own API key field -- first non-empty wins. Usage counts against the caller's own RapidAPI plan, not ours; every response reports what it spent and what is left in api_usage.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum trips to return, after merging and sorting.
nightsNoTrip length in nights; a number, or a list like [5, 6, 7]. The return date is derived from each departure date.
sort_byNo"best", "price", or "duration". Applied across all results.best
currencyNoISO currency code, default "usd".usd
max_priceNoOnly return trips at or below this total price.
seat_typeNo1 economy, 2 premium economy, 3 business, 4 first.
passengersNoPassenger counts as [adults, children, infants].
to_airportYesDestination airport. One IATA code ("BCN"), several separated by commas ("BCN,LIS,ATH"), or a list (["BCN","LIS","ATH"]) -- every shape is accepted and the destinations are compared in the same search.
return_dateNoFixed return date. Use this OR nights, not both.
from_airportYesOrigin IATA code, e.g. "TLV". One origin per search; a second one is refused rather than searched.
max_searchesNoCap the billed requests this call may make. Lower it to spend less of the plan's quota on a wide search; the range is then sampled evenly rather than cut short.
use_fallbackNoLeave unset. Switches the search to a second, independent flight data source instead of the usual Google Flights page read. Unset already escalates to that source once, automatically, after a search's retries have failed. true forces it inline on every attempt -- much slower, and it can time out. false disables it entirely, that automatic retry included.
departure_dateNoSingle outbound date, "YYYY-MM-DD".
max_return_stopsNoMaximum stops on the return leg.
departure_date_toNoLast date of an outbound range.
departure_date_fromNoFirst date of an outbound range.
max_departure_stopsNoMaximum stops on the outbound leg.
return_airline_codesNoRestrict the return leg to these airlines.
departure_airline_codesNoRestrict the outbound leg to these airlines.

Output Schema

ParametersJSON Schema
NameRequiredDescription
messageNoPresent when there is something the model must relay to the user rather than silently absorb -- no results, a degraded search, a missing key or a spent quota.
partialNoPresent when some searches failed but others succeeded. Plain text saying how much of the request the results cover.
resultsYesThe itineraries or properties found, already sorted and deduplicated. An empty array is only meaningful when search_status is 'empty'.
api_usageNoWhat this call cost the caller's own RapidAPI plan, and what remains on it. Present on every response that reached the upstream, including a degraded one -- a search that failed was still billed.
signup_urlNoWhere the caller subscribes or changes plan.
result_countNo
needs_api_keyNoTrue when no usable RapidAPI key arrived with the call, or the upstream rejected the one that did. No search was run and nothing was billed; signup_url and message say how to fix it.
search_statusNoWhether the underlying search actually completed, read from the backend's X-Search-Status header. 'ok': every combination searched returned results. 'empty': the search completed and Google genuinely has no itineraries for it -- a real answer, not a failure. 'partial': some combinations returned results and some failed, so the list is incomplete. 'degraded': every combination failed, so the search did not happen and an empty list means nothing; this case is also flagged with isError: true and is safe to retry.
by_destinationNoOne entry per destination the REQUEST asked for, in request order, present whether or not that destination has any flights in `results`. A destination with an empty `rows` array is a hole in the answer, and `reason` says which kind of hole: 'no_flights' (searched, answered, Google has nothing), 'search_failed' (searched and the search errored, so nothing is known), 'not_in_limit' (searched, found flights, none fitted in `limit`) or 'not_searched' (never searched -- the per-call fan-out cap sampled it away). 'ok' means it has rows. Read this rather than inferring coverage from `results`: a destination missing from `results` looks identical to one that has no flights, and they are not the same answer. `rows` are the same row objects that are in `results`, in the same order -- nothing here is data the answer does not already contain.
quota_exhaustedNoTrue when the caller's RapidAPI plan has no requests left for the current period.
search_coverageNoWhat was actually searched. Present whether or not the request was truncated, so a model can state honestly what its answer rests on.

TDQS

A4.8/5.0
Behavior5/5

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

The description discloses much more than the annotations alone: every date/destination combination is one billed request, quota usage is reported in api_usage, fallback behavior and its performance trade-offs are explained, and empty destination entries come with a reason. It also explains that the caller's own RapidAPI key is used, which is critical operational context. No contradiction with the read-only annotation.

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 long but dense and every section earns its place: purpose, usage pattern, billing model, output field guidance, and authentication. The most important scoping and usage information is front-loaded, and the structure is 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 complex tool with 19 parameters, external API-key requirements, per-request billing, and fallback behavior, the description covers all the essential context an agent needs. It explains authentication, quota attribution, how to interpret destination entries, and how to control search costs, making it complete despite the rich schema and output schema.

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?

Although schema coverage is 100%, the description adds meaning beyond the schema: it explains the flexible search pattern using departure_date_from/departure_date_to plus nights, the multi-destination input formats, max_searches sampling behavior, and the use_fallback escalation semantics. This materially helps an agent choose and fill parameters correctly.

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 states a specific verb and resource: search round-trip flights with live prices from Google Flights. It further specifies that results are priced as paired legs rather than two separate one-ways, which clearly distinguishes this tool from the sibling search_oneway_flights even without naming it.

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 explicitly says 'Use it for any return-trip fare question' and gives a detailed example of when to make a single flexible call. It does not explicitly name the one-way sibling as an alternative or state 'do not use for one-way searches,' so it stops short of the full when/when-not/alternatives guidance.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updates
    • Changedsearch_oneway_flights5 fields changed
      • removedOutput schema / properties / by_destination / additionalProperties / properties / cheapest / additionalProperties
        Removed value: -true
      • addedOutput schema / properties / by_destination / additionalProperties / properties / cheapest / anyOf
        Added value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
      • removedOutput schema / properties / by_destination / additionalProperties / properties / cheapest / type
        Removed value: -[
-  "object",
-  "null"
-]
      • addedOutput schema / properties / by_destination / additionalProperties / properties / dates / additionalProperties / properties / cheapest_price / anyOf
        Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
      • removedOutput schema / properties / by_destination / additionalProperties / properties / dates / additionalProperties / properties / cheapest_price / type
        Removed value: -[
-  "number",
-  "null"
-]
    • Changedsearch_roundtrip_flights5 fields changed
      • removedOutput schema / properties / by_destination / additionalProperties / properties / cheapest / additionalProperties
        Removed value: -true
      • addedOutput schema / properties / by_destination / additionalProperties / properties / cheapest / anyOf
        Added value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
      • removedOutput schema / properties / by_destination / additionalProperties / properties / cheapest / type
        Removed value: -[
-  "object",
-  "null"
-]
      • addedOutput schema / properties / by_destination / additionalProperties / properties / dates / additionalProperties / properties / cheapest_price / anyOf
        Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
      • removedOutput schema / properties / by_destination / additionalProperties / properties / dates / additionalProperties / properties / cheapest_price / type
        Removed value: -[
-  "number",
-  "null"
-]
  2. 2 tool updates
    • Changedsearch_oneway_flights1 field changed
      • addedOutput schema / properties / by_destination
        Added value: +{
+  "additionalProperties": {
+    "additionalProperties": true,
+    "properties": {
+      "cheapest": {
+        "additionalProperties": true,
+        "description": "The lowest-priced of this destination's rows in `results`, or null when it has none.",
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "dates": {
+        "additionalProperties": {
+          "additionalProperties": true,
+          "properties": {
+            "cheapest_price": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "reason": {
+              "enum": [
+                "ok",
+                "no_flights",
+                "search_failed",
+                "not_in_limit",
+                "not_searched"
+              ],
+              "type": "string"
+            },
+            "row_count": {
+              "minimum": 0,
+              "type": "integer"
+            },
+            "searched": {
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        },
+        "description": "Present only on multi-date searches: one entry per departure date requested for this destination, so a date the fan-out cap sampled away is visible rather than absent. `cheapest_price` is null when that date has no row in `results`.",
+        "type": "object"
+      },
+      "reason": {
+        "enum": [
+          "ok",
+          "no_flights",
+          "search_failed",
+          "not_in_limit",
+          "not_searched"
+        ],
+        "type": "string"
+      },
+      "rows": {
+        "items": {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "searched": {
+        "description": "Whether at least one search actually ran for this destination. False means the fan-out cap dropped it.",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "rows",
+      "searched",
+      "reason"
+    ],
+    "type": "object"
+  },
+  "description": "One entry per destination the REQUEST asked for, in request order, present whether or not that destination has any flights in `results`. A destination with an empty `rows` array is a hole in the answer, and `reason` says which kind of hole: 'no_flights' (searched, answered, Google has nothing), 'search_failed' (searched and the search errored, so nothing is known), 'not_in_limit' (searched, found flights, none fitted in `limit`) or 'not_searched' (never searched -- the per-call fan-out cap sampled it away). 'ok' means it has rows.\n\nRead this rather than inferring coverage from `results`: a destination missing from `results` looks identical to one that has no flights, and they are not the same answer. `rows` are the same row objects that are in `results`, in the same order -- nothing here is data the answer does not already contain.",
+  "type": "object"
+}
    • Changedsearch_roundtrip_flights1 field changed
      • addedOutput schema / properties / by_destination
        Added value: +{
+  "additionalProperties": {
+    "additionalProperties": true,
+    "properties": {
+      "cheapest": {
+        "additionalProperties": true,
+        "description": "The lowest-priced of this destination's rows in `results`, or null when it has none.",
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "dates": {
+        "additionalProperties": {
+          "additionalProperties": true,
+          "properties": {
+            "cheapest_price": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "reason": {
+              "enum": [
+                "ok",
+                "no_flights",
+                "search_failed",
+                "not_in_limit",
+                "not_searched"
+              ],
+              "type": "string"
+            },
+            "row_count": {
+              "minimum": 0,
+              "type": "integer"
+            },
+            "searched": {
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        },
+        "description": "Present only on multi-date searches: one entry per departure date requested for this destination, so a date the fan-out cap sampled away is visible rather than absent. `cheapest_price` is null when that date has no row in `results`.",
+        "type": "object"
+      },
+      "reason": {
+        "enum": [
+          "ok",
+          "no_flights",
+          "search_failed",
+          "not_in_limit",
+          "not_searched"
+        ],
+        "type": "string"
+      },
+      "rows": {
+        "items": {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "searched": {
+        "description": "Whether at least one search actually ran for this destination. False means the fan-out cap dropped it.",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "rows",
+      "searched",
+      "reason"
+    ],
+    "type": "object"
+  },
+  "description": "One entry per destination the REQUEST asked for, in request order, present whether or not that destination has any flights in `results`. A destination with an empty `rows` array is a hole in the answer, and `reason` says which kind of hole: 'no_flights' (searched, answered, Google has nothing), 'search_failed' (searched and the search errored, so nothing is known), 'not_in_limit' (searched, found flights, none fitted in `limit`) or 'not_searched' (never searched -- the per-call fan-out cap sampled it away). 'ok' means it has rows.\n\nRead this rather than inferring coverage from `results`: a destination missing from `results` looks identical to one that has no flights, and they are not the same answer. `rows` are the same row objects that are in `results`, in the same order -- nothing here is data the answer does not already contain.",
+  "type": "object"
+}
  3. 2 tool updates
    • Changedsearch_oneway_flights2 fields changed
      • changedInput schema / properties / from_airport / description
        Previous value: -"Origin IATA code, e.g. \"TLV\"."New value: +"Origin IATA code, e.g. \"TLV\". One origin per search; a second one is refused rather than searched."
      • changedInput schema / properties / to_airport / description
        Previous value: -"Destination IATA code, or a list of them to compare."New value: +"Destination airport. One IATA code (\"BCN\"), several separated by commas (\"BCN,LIS,ATH\"), or a list ([\"BCN\",\"LIS\",\"ATH\"]) -- every shape is accepted and the destinations are compared in the same search."
    • Changedsearch_roundtrip_flights2 fields changed
      • changedInput schema / properties / from_airport / description
        Previous value: -"Origin IATA code, e.g. \"TLV\"."New value: +"Origin IATA code, e.g. \"TLV\". One origin per search; a second one is refused rather than searched."
      • changedInput schema / properties / to_airport / description
        Previous value: -"Destination IATA code, or a list of them to compare."New value: +"Destination airport. One IATA code (\"BCN\"), several separated by commas (\"BCN,LIS,ATH\"), or a list ([\"BCN\",\"LIS\",\"ATH\"]) -- every shape is accepted and the destinations are compared in the same search."
  4. 2 tool updates
    • Changedsearch_oneway_flights4 fields changed
      • addedOutput schema / description
        Added value: +"A completed flight search. Read search_status before reading results: an empty array means 'no flights' only when search_status is 'empty'."
      • addedOutput schema / properties
        Added value: +{
+  "api_usage": {
+    "additionalProperties": true,
+    "description": "What this call cost the caller's own RapidAPI plan, and what remains on it. Present on every response that reached the upstream, including a degraded one -- a search that failed was still billed.",
+    "properties": {
+      "note": {
+        "description": "The same figures as a sentence, for the model to relay.",
+        "type": "string"
+      },
+      "plan_requests_limit": {
+        "type": "integer"
+      },
+      "plan_requests_remaining": {
+        "type": "integer"
+      },
+      "requests_used_by_this_call": {
+        "minimum": 0,
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  },
+  "message": {
+    "description": "Present when there is something the model must relay to the user rather than silently absorb -- no results, a degraded search, a missing key or a spent quota.",
+    "type": "string"
+  },
+  "needs_api_key": {
+    "description": "True when no usable RapidAPI key arrived with the call, or the upstream rejected the one that did. No search was run and nothing was billed; signup_url and message say how to fix it.",
+    "type": "boolean"
+  },
+  "partial": {
+    "description": "Present when some searches failed but others succeeded. Plain text saying how much of the request the results cover.",
+    "type": "string"
+  },
+  "quota_exhausted": {
+    "description": "True when the caller's RapidAPI plan has no requests left for the current period.",
+    "type": "boolean"
+  },
+  "result_count": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "results": {
+    "description": "The itineraries or properties found, already sorted and deduplicated. An empty array is only meaningful when search_status is 'empty'.",
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "search_coverage": {
+    "additionalProperties": true,
+    "description": "What was actually searched. Present whether or not the request was truncated, so a model can state honestly what its answer rests on.",
+    "properties": {
+      "departure_dates_searched": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "destinations_searched": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "max_searches_per_request": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "note": {
+        "type": "string"
+      },
+      "requested_combinations": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "searched_combinations": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "truncated": {
+        "description": "True when the request expanded past this call's spend ceiling and was sampled. A date absent from departure_dates_searched was never searched, which is not the same as having no flights.",
+        "type": "boolean"
+      }
+    },
+    "type": "object"
+  },
+  "search_status": {
+    "description": "Whether the underlying search actually completed, read from the backend's X-Search-Status header. 'ok': every combination searched returned results. 'empty': the search completed and Google genuinely has no itineraries for it -- a real answer, not a failure. 'partial': some combinations returned results and some failed, so the list is incomplete. 'degraded': every combination failed, so the search did not happen and an empty list means nothing; this case is also flagged with isError: true and is safe to retry.",
+    "enum": [
+      "ok",
+      "empty",
+      "partial",
+      "degraded"
+    ],
+    "type": "string"
+  },
+  "signup_url": {
+    "description": "Where the caller subscribes or changes plan.",
+    "type": "string"
+  }
+}
      • addedOutput schema / required
        Added value: +[
+  "results"
+]
      • addedOutput schema / title
        Added value: +"Flight search result"
    • Changedsearch_roundtrip_flights4 fields changed
      • addedOutput schema / description
        Added value: +"A completed flight search. Read search_status before reading results: an empty array means 'no flights' only when search_status is 'empty'."
      • addedOutput schema / properties
        Added value: +{
+  "api_usage": {
+    "additionalProperties": true,
+    "description": "What this call cost the caller's own RapidAPI plan, and what remains on it. Present on every response that reached the upstream, including a degraded one -- a search that failed was still billed.",
+    "properties": {
+      "note": {
+        "description": "The same figures as a sentence, for the model to relay.",
+        "type": "string"
+      },
+      "plan_requests_limit": {
+        "type": "integer"
+      },
+      "plan_requests_remaining": {
+        "type": "integer"
+      },
+      "requests_used_by_this_call": {
+        "minimum": 0,
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  },
+  "message": {
+    "description": "Present when there is something the model must relay to the user rather than silently absorb -- no results, a degraded search, a missing key or a spent quota.",
+    "type": "string"
+  },
+  "needs_api_key": {
+    "description": "True when no usable RapidAPI key arrived with the call, or the upstream rejected the one that did. No search was run and nothing was billed; signup_url and message say how to fix it.",
+    "type": "boolean"
+  },
+  "partial": {
+    "description": "Present when some searches failed but others succeeded. Plain text saying how much of the request the results cover.",
+    "type": "string"
+  },
+  "quota_exhausted": {
+    "description": "True when the caller's RapidAPI plan has no requests left for the current period.",
+    "type": "boolean"
+  },
+  "result_count": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "results": {
+    "description": "The itineraries or properties found, already sorted and deduplicated. An empty array is only meaningful when search_status is 'empty'.",
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "search_coverage": {
+    "additionalProperties": true,
+    "description": "What was actually searched. Present whether or not the request was truncated, so a model can state honestly what its answer rests on.",
+    "properties": {
+      "departure_dates_searched": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "destinations_searched": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "max_searches_per_request": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "note": {
+        "type": "string"
+      },
+      "requested_combinations": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "searched_combinations": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "truncated": {
+        "description": "True when the request expanded past this call's spend ceiling and was sampled. A date absent from departure_dates_searched was never searched, which is not the same as having no flights.",
+        "type": "boolean"
+      }
+    },
+    "type": "object"
+  },
+  "search_status": {
+    "description": "Whether the underlying search actually completed, read from the backend's X-Search-Status header. 'ok': every combination searched returned results. 'empty': the search completed and Google genuinely has no itineraries for it -- a real answer, not a failure. 'partial': some combinations returned results and some failed, so the list is incomplete. 'degraded': every combination failed, so the search did not happen and an empty list means nothing; this case is also flagged with isError: true and is safe to retry.",
+    "enum": [
+      "ok",
+      "empty",
+      "partial",
+      "degraded"
+    ],
+    "type": "string"
+  },
+  "signup_url": {
+    "description": "Where the caller subscribes or changes plan.",
+    "type": "string"
+  }
+}
      • addedOutput schema / required
        Added value: +[
+  "results"
+]
      • addedOutput schema / title
        Added value: +"Flight search result"
  5. 2 tool updates
    • Changedsearch_oneway_flights23 fields changed
      • addedInput schema / properties / airline_codes / description
        Added value: +"Restrict to these airline codes, e.g. [\"LY\"]."
      • addedInput schema / properties / arrival_time_max / description
        Added value: +"Latest arrival hour, 0-23."
      • addedInput schema / properties / arrival_time_min / description
        Added value: +"Earliest arrival hour, 0-23."
      • addedInput schema / properties / currency / description
        Added value: +"ISO currency code, default \"usd\"."
      • addedInput schema / properties / departure_date / description
        Added value: +"Single departure date, \"YYYY-MM-DD\"."
      • addedInput schema / properties / departure_date_from / description
        Added value: +"First date of a departure range."
      • addedInput schema / properties / departure_date_to / description
        Added value: +"Last date of a departure range."
      • addedInput schema / properties / departure_time_max / description
        Added value: +"Latest departure hour, 0-23."
      • addedInput schema / properties / departure_time_min / description
        Added value: +"Earliest departure hour, 0-23."
      • addedInput schema / properties / exclude_airline_codes / description
        Added value: +"Exclude these airline codes."
      • addedInput schema / properties / from_airport / description
        Added value: +"Origin IATA code, e.g. \"TLV\"."
      • addedInput schema / properties / limit / description
        Added value: +"Maximum flights to return, after merging and sorting."
      • addedInput schema / properties / max_price / description
        Added value: +"Only return flights at or below this price."
      • addedInput schema / properties / max_searches / description
        Added value: +"Cap the billed requests this call may make. Lower it to spend less of the plan's quota on a wide search; the range is then sampled evenly rather than cut short."
      • addedInput schema / properties / max_stops / description
        Added value: +"Maximum stops per flight. 0 means non-stop only."
      • addedInput schema / properties / passengers / description
        Added value: +"Passenger counts as [adults, children, infants]."
      • addedInput schema / properties / seat_type / description
        Added value: +"1 economy, 2 premium economy, 3 business, 4 first."
      • addedInput schema / properties / sort_by / description
        Added value: +"\"best\", \"price\", or \"duration\". Applied across all results."
      • addedInput schema / properties / to_airport / description
        Added value: +"Destination IATA code, or a list of them to compare."
      • addedInput schema / properties / use_fallback / anyOf
        Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
      • changedInput schema / properties / use_fallback / default
        Previous value: -falseNew value: +null
      • addedInput schema / properties / use_fallback / description
        Added value: +"Leave unset. Switches the search to a second, independent flight data source instead of the usual Google Flights page read. Unset already escalates to that source once, automatically, after a search's retries have failed. true forces it inline on every attempt -- much slower, and it can time out. false disables it entirely, that automatic retry included."
      • removedInput schema / properties / use_fallback / type
        Removed value: -"boolean"
    • Changedsearch_roundtrip_flights22 fields changed
      • addedInput schema / properties / currency / description
        Added value: +"ISO currency code, default \"usd\"."
      • addedInput schema / properties / departure_airline_codes / description
        Added value: +"Restrict the outbound leg to these airlines."
      • addedInput schema / properties / departure_date / description
        Added value: +"Single outbound date, \"YYYY-MM-DD\"."
      • addedInput schema / properties / departure_date_from / description
        Added value: +"First date of an outbound range."
      • addedInput schema / properties / departure_date_to / description
        Added value: +"Last date of an outbound range."
      • addedInput schema / properties / from_airport / description
        Added value: +"Origin IATA code, e.g. \"TLV\"."
      • addedInput schema / properties / limit / description
        Added value: +"Maximum trips to return, after merging and sorting."
      • addedInput schema / properties / max_departure_stops / description
        Added value: +"Maximum stops on the outbound leg."
      • addedInput schema / properties / max_price / description
        Added value: +"Only return trips at or below this total price."
      • addedInput schema / properties / max_return_stops / description
        Added value: +"Maximum stops on the return leg."
      • addedInput schema / properties / max_searches / description
        Added value: +"Cap the billed requests this call may make. Lower it to spend less of the plan's quota on a wide search; the range is then sampled evenly rather than cut short."
      • addedInput schema / properties / nights / description
        Added value: +"Trip length in nights; a number, or a list like [5, 6, 7]. The return date is derived from each departure date."
      • addedInput schema / properties / passengers / description
        Added value: +"Passenger counts as [adults, children, infants]."
      • addedInput schema / properties / return_airline_codes / description
        Added value: +"Restrict the return leg to these airlines."
      • addedInput schema / properties / return_date / description
        Added value: +"Fixed return date. Use this OR nights, not both."
      • addedInput schema / properties / seat_type / description
        Added value: +"1 economy, 2 premium economy, 3 business, 4 first."
      • addedInput schema / properties / sort_by / description
        Added value: +"\"best\", \"price\", or \"duration\". Applied across all results."
      • addedInput schema / properties / to_airport / description
        Added value: +"Destination IATA code, or a list of them to compare."
      • addedInput schema / properties / use_fallback / anyOf
        Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
      • changedInput schema / properties / use_fallback / default
        Previous value: -falseNew value: +null
      • addedInput schema / properties / use_fallback / description
        Added value: +"Leave unset. Switches the search to a second, independent flight data source instead of the usual Google Flights page read. Unset already escalates to that source once, automatically, after a search's retries have failed. true forces it inline on every attempt -- much slower, and it can time out. false disables it entirely, that automatic retry included."
      • removedInput schema / properties / use_fallback / type
        Removed value: -"boolean"
  6. 2 tool updates
    • First observedsearch_oneway_flights
    • First observedsearch_roundtrip_flights

Frequently Asked Questions

Discussions

No comments yet. Be the first to start the discussion!

Login with GitHub to comment

Related MCP Connectors

Related MCP Servers

  • google-flights-mcp

    thealexauer
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server that enables Google Flights search via SerpApi, supporting one-way, round-trip, and multi-city itineraries with defaults for Business class, Star Alliance, and EUR pricing. It provides flight search, booking options, and usage tracking.
    234
    MIT

  • whentofly

    dimabalony
    A
    license
    Not graded
    quality
    B
    maintenance
    Flight search for AI agents: flexible-date cheapest round-trips with a good-price verdict from historical data. Hosted remote MCP, free, no key.
    3
    MIT

  • Google Flights MCP

    impca201
    F
    license
    Not graded
    quality
    Not graded
    maintenance
    A remote MCP server that searches Google Flights for flight information and airport codes. It enables users to find flights, locate airports, and generate travel dates through natural language interactions.
    -
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources