viajante

Overview Schema Source Related Servers Discussions Admin

Search flights

search_flights

Read-onlyIdempotent

Search Google Flights for named routes and dates, compare fares, filter stops, cabins, and airlines, and return prices with booking links.

Instructions

Google Flights search for named routes and dates. Each routes entry is ORIGIN-DEST:YYYY-MM-DD. Use search_dates for the cheapest week and search_flex for +/-N days. fetch=detail needs the browser extra and Chromium. Currency is currency, or inferred from a named origin's owned country; if unproven, ask. Viajante does not convert. Do not invent a bag fee. max_stops is 0, 1 or 2. Metro codes (LON, NYC) expand on one-way and rt routes. One-way searches send clock bounds, max_duration, max_layover, price_cap, less_emissions and hide_separate_tickets to the page, and check each one locally. exclude_basic_economy is refused. nearby_days (default 0, off) adds a ±N cheapest-fare grid on that search; round trips shift both dates and keep the trip length. The grid reuses the date calendar and does not change offers. A successful query carries price_insight when the page states a level (low, typical, or high) that matches its heading. That level is Google's label for the current price against its typical range, not a forecast. include_price_history adds the page's own price history and is off by default. A successful query may carry recommendation: evidence, not a verdict. Check relaxed_requirements before calling it a match. After a named hub or leisure trunk, search_hidden_city may run once with the same route and date, never when bags were named. Rules and wording: get_guide.

    deadline_seconds stops starting queries after that many seconds; unfinished
    queries are error code deadline (not loaded, not empty). See get_guide.

Input Schema

TableJSON Schema

Name	Required	Default
`top`	No
`via`	No
`bags`	No
`sort`	No	ranked
`trip`	No	one-way
`cabin`	No	economy
`fetch`	No	auto
`proxy`	No
`adults`	No
`nearby`	No
`routes`	Yes
`country`	No
`airlines`	No
`alliance`	No
`carry_on`	No
`children`	No
`currency`	No
`max_stops`	No
`price_cap`	No
`exclude_via`	No
`max_layover`	No
`min_layover`	No
`nearby_days`	No
`arrive_after`	No
`depart_after`	No
`max_duration`	No
`no_overnight`	No
`arrive_before`	No
`depart_before`	No
`depart_window`	No
`baggage_buffer`	No
`infants_on_lap`	No
`less_emissions`	No
`infants_in_seat`	No
`deadline_seconds`	No
`exclude_airlines`	No
`exclude_airports`	No
`exclude_alliance`	No
`include_airports`	No
`require_overnight`	No
`exclude_basic_economy`	No
`hide_separate_tickets`	No
`include_price_history`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`empty_note`	Yes
`error_code`	Yes
`observed_at`	Yes
`retry_after`	Yes
`completeness`	Yes
`empty_reason`	Yes
`observed_at_basis`	Yes
`retry_after_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed45 schema fields changedv1.5.2Oct 19, 2026

removedInput schema / properties / adults / title
```
Removed value: -"Adults"
```
removedInput schema / properties / airlines / title
```
Removed value: -"Airlines"
```
removedInput schema / properties / alliance / title
```
Removed value: -"Alliance"
```

addedInput schema / properties / arrive_after

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

removedInput schema / properties / arrive_before / title
```
Removed value: -"Arrive Before"
```
removedInput schema / properties / baggage_buffer / title
```
Removed value: -"Baggage Buffer"
```
removedInput schema / properties / bags / title
```
Removed value: -"Bags"
```
removedInput schema / properties / cabin / title
```
Removed value: -"Cabin"
```
removedInput schema / properties / carry_on / title
```
Removed value: -"Carry On"
```
removedInput schema / properties / children / title
```
Removed value: -"Children"
```
removedInput schema / properties / country / title
```
Removed value: -"Country"
```
removedInput schema / properties / currency / title
```
Removed value: -"Currency"
```

addedInput schema / properties / deadline_seconds

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

removedInput schema / properties / depart_after / title
```
Removed value: -"Depart After"
```

addedInput schema / properties / depart_before

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

removedInput schema / properties / depart_window / title
```
Removed value: -"Depart Window"
```
removedInput schema / properties / exclude_airlines / title
```
Removed value: -"Exclude Airlines"
```
removedInput schema / properties / exclude_airports / title
```
Removed value: -"Exclude Airports"
```
removedInput schema / properties / exclude_alliance / title
```
Removed value: -"Exclude Alliance"
```

addedInput schema / properties / exclude_basic_economy

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

removedInput schema / properties / exclude_via / title
```
Removed value: -"Exclude Via"
```
removedInput schema / properties / fetch / title
```
Removed value: -"Fetch"
```

addedInput schema / properties / hide_separate_tickets

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

removedInput schema / properties / include_airports / title
```
Removed value: -"Include Airports"
```

addedInput schema / properties / include_price_history

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

removedInput schema / properties / infants_in_seat / title
```
Removed value: -"Infants In Seat"
```
removedInput schema / properties / infants_on_lap / title
```
Removed value: -"Infants On Lap"
```

addedInput schema / properties / less_emissions

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

removedInput schema / properties / max_duration / title
```
Removed value: -"Max Duration"
```
removedInput schema / properties / max_layover / title
```
Removed value: -"Max Layover"
```
removedInput schema / properties / max_stops / title
```
Removed value: -"Max Stops"
```
removedInput schema / properties / min_layover / title
```
Removed value: -"Min Layover"
```
removedInput schema / properties / nearby / title
```
Removed value: -"Nearby"
```

addedInput schema / properties / nearby_days

Added value: +{
+  "default": 0,
+  "type": "integer"
+}

removedInput schema / properties / no_overnight / title
```
Removed value: -"No Overnight"
```
removedInput schema / properties / price_cap / title
```
Removed value: -"Price Cap"
```
removedInput schema / properties / proxy / title
```
Removed value: -"Proxy"
```
removedInput schema / properties / require_overnight / title
```
Removed value: -"Require Overnight"
```
removedInput schema / properties / routes / title
```
Removed value: -"Routes"
```
removedInput schema / properties / sort / title
```
Removed value: -"Sort"
```
removedInput schema / properties / top / title
```
Removed value: -"Top"
```
removedInput schema / properties / trip / title
```
Removed value: -"Trip"
```
removedInput schema / properties / via / title
```
Removed value: -"Via"
```

removedInput schema / title

Removed value: -"search_flightsArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "completeness": {
+      "enum": [
+        "complete",
+        "partial",
+        "blocked"
+      ],
+      "type": "string"
+    },
+    "empty_note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "empty_reason": {
+      "anyOf": [
+        {
+          "enum": [
+            "provider_empty",
+            "filtered_out",
+            "not_loaded"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "error_code": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "observed_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "observed_at_basis": {
+      "anyOf": [
+        {
+          "enum": [
+            "provider",
+            "fetch"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "retry_after": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "retry_after_seconds": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "status": {
+      "enum": [
+        "ok",
+        "no_results",
+        "rate_limited",
+        "blocked",
+        "timeout",
+        "failed"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "completeness",
+    "empty_reason",
+    "empty_note",
+    "error_code",
+    "retry_after",
+    "retry_after_seconds",
+    "observed_at",
+    "observed_at_basis"
+  ],
+  "type": "object"
+}

First observedv1.0.0Sep 9, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the read-only annotations, it discloses important behavior: currency inference and no conversion, refusal of exclude_basic_economy, how nearby_days builds a separate cheapest-fare grid, deadline_seconds producing error code 'deadline' rather than an empty result, and that price_insight is Google's label, not a forecast.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The opening is front-loaded and information-dense, with little filler. However, the body is a run-on stream of clauses with no grouping or headings, and the trailing deadline_seconds block has awkward indentation, making the definition hard to scan despite its useful content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema means return values need not be explained, and annotations cover the safety profile. The description captures several critical gotchas for a complex search tool, but it does not fully equip an agent to use a 43-parameter surface whose schema has no per-field descriptions.

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

Parameters2/5

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

With 43 parameters and 0% schema description coverage, the description must carry parameter meaning but only explains a subset: routes format, max_stops values, nearby_days, include_price_history, deadline_seconds, fetch, currency, and exclude_basic_economy. Many parameters such as top, via, sort, cabin, proxy, airlines, alliance, min_layover, and the clock-bound fields are left without semantic guidance.

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 first sentence names a specific verb and resource ('Google Flights search') plus the required route format 'ORIGIN-DEST:YYYY-MM-DD'. It also distinguishes this tool from search_dates and search_flex, so an agent can identify it without opening sibling schemas.

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 explicitly routes alternatives: 'Use search_dates for the cheapest week and search_flex for +/-N days', and constrains search_hidden_city to one run after a named hub or leisure trunk, never when bags were named. It also points to get_guide for rules and wording.

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