seats.aero MCP server

get_flights

Read-onlyIdempotent

Search award flight availability by origin, destination, date, and cabin class, using cached seats.aero data to find flights bookable with miles.

Instructions

Get cached award flights on seats.aero.

Input Schema

TableJSON Schema

Name	Required	Description
`skip`	No	Number of already-retrieved results to skip.
`take`	No	Maximum results to return (10-1000; default 500).
`cabins`	No	Cabins that must be available, comma-delimited when specifying multiple cabins.
`cursor`	No	Opaque cursor returned by the first page of this search.
`endDate`	No	Latest departure date, in YYYY-MM-DD format.
`sources`	No	Mileage program sources, comma-delimited when specifying multiple.
`carriers`	No	Two-character carrier codes, comma-delimited (for example, DL,AA).
`order_by`	No	Set to lowest_mileage to return the cheapest results first.
`startDate`	No	Earliest departure date, in YYYY-MM-DD format.
`cabinClass`	No	Deprecated single-cabin alias for cabins.
`minify_trips`	No	Return fewer trip fields when include_trips is enabled.
`departureDate`	No	Deprecated single-date alias. When startDate or endDate is omitted, this value is used for that bound.
`include_trips`	No	Include flight-level trip details in each availability result.
`originAirport`	Yes	Origin airport codes, comma-delimited when searching multiple airports (for example, SFO,LAX).
`include_filtered`	No	Include raw results normally removed by dynamic-price filters.
`destinationAirport`	Yes	Destination airport codes, comma-delimited when searching multiple airports (for example, FRA,LHR).
`only_direct_flights`	No	Only return results with a direct flight available.

Schema Changelog

Changes observed during successful MCP inspections.

Changed36 schema fields changedv1.2.0Aug 10, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / cabinClass / description

Added value: +"Deprecated single-cabin alias for cabins."

addedInput schema / properties / cabins

Added value: +{
+  "description": "Cabins that must be available, comma-delimited when specifying multiple cabins.",
+  "pattern": "^(economy|premium|business|first)(,(economy|premium|business|first))*$",
+  "type": "string"
+}

addedInput schema / properties / carriers / description

Added value: +"Two-character carrier codes, comma-delimited (for example, DL,AA)."

removedInput schema / properties / carriers / maxLength
```
Removed value: -2
```
removedInput schema / properties / carriers / minLength
```
Removed value: -2
```

addedInput schema / properties / carriers / pattern

Added value: +"^[A-Za-z0-9]{2}(,[A-Za-z0-9]{2})*$"

addedInput schema / properties / cursor / description

Added value: +"Opaque cursor returned by the first page of this search."

addedInput schema / properties / cursor / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / cursor / minimum
```
Added value: +0
```

changedInput schema / properties / cursor / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / departureDate / description

Added value: +"Deprecated single-date alias. When startDate or endDate is omitted, this value is used for that bound."

addedInput schema / properties / departureDate / pattern

Added value: +"^\\d{4}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])$"

addedInput schema / properties / destinationAirport / description

Added value: +"Destination airport codes, comma-delimited when searching multiple airports (for example, FRA,LHR)."

addedInput schema / properties / destinationAirport / pattern
```
Added value: +"^[A-Za-z]{3}(,[A-Za-z]{3})*$"
```

addedInput schema / properties / endDate / description

Added value: +"Latest departure date, in YYYY-MM-DD format."

changedInput schema / properties / endDate / pattern

Previous value: -"^\\d{4}\\-(0[1-9]|1[012])\\-(0[1-9]|[12][0-9]|3[01])$"New value: +"^\\d{4}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])$"

addedInput schema / properties / include_filtered

Added value: +{
+  "description": "Include raw results normally removed by dynamic-price filters.",
+  "type": "boolean"
+}

addedInput schema / properties / include_trips / description

Added value: +"Include flight-level trip details in each availability result."

addedInput schema / properties / minify_trips

Added value: +{
+  "description": "Return fewer trip fields when include_trips is enabled.",
+  "type": "boolean"
+}

addedInput schema / properties / only_direct_flights / description

Added value: +"Only return results with a direct flight available."

addedInput schema / properties / order_by / const
```
Added value: +"lowest_mileage"
```

addedInput schema / properties / order_by / description

Added value: +"Set to lowest_mileage to return the cheapest results first."

removedInput schema / properties / order_by / enum

Removed value: -[
-  "",
-  "lowest_mileage"
-]

addedInput schema / properties / originAirport / description

Added value: +"Origin airport codes, comma-delimited when searching multiple airports (for example, SFO,LAX)."

addedInput schema / properties / originAirport / pattern
```
Added value: +"^[A-Za-z]{3}(,[A-Za-z]{3})*$"
```

addedInput schema / properties / skip / description

Added value: +"Number of already-retrieved results to skip."

addedInput schema / properties / skip / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / skip / minimum
```
Added value: +0
```

changedInput schema / properties / skip / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / sources

Added value: +{
+  "description": "Mileage program sources, comma-delimited when specifying multiple.",
+  "type": "string"
+}

addedInput schema / properties / startDate / description

Added value: +"Earliest departure date, in YYYY-MM-DD format."

changedInput schema / properties / startDate / pattern

Previous value: -"^\\d{4}\\-(0[1-9]|1[012])\\-(0[1-9]|[12][0-9]|3[01])$"New value: +"^\\d{4}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])$"

addedInput schema / properties / take / description

Added value: +"Maximum results to return (10-1000; default 500)."

changedInput schema / properties / take / type

Previous value: -"number"New value: +"integer"

First observedv1.0.0Jun 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds the 'cached' nature, which signals possibly stale data, but gives no further behavioral details such as pagination or data freshness. With annotations present, the incremental context is moderate.

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?

A single, front-loaded sentence with zero wasted words. It immediately communicates the core action, and the schema handles all technical detail, so this brevity is appropriate.

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

Completeness2/5

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

This tool has 17 parameters and no output schema, yet the description is only one sentence. It does not explain the return shape, pagination, the meaning of cursor, or how include_trips affects results. The schema covers parameter meaning, but the description leaves the agent without essential behavioral context.

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% (all 17 parameters have meaningful descriptions), and the tool description adds no parameter-level semantics. The baseline of 3 applies because the schema carries the full burden of parameter explanation.

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 ('Get') and resource ('cached award flights') on seats.aero, clearly distinguishing it from sibling tools like live_search (cached vs. live) and get_trips/get_routes (award flights vs. trips/routes).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use guidance is provided. The word 'cached' implies this tool serves cached data rather than live searches, but it does not name alternatives like live_search or refresh_cached_data. Usage context is only implied.

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

Deploy Server

get_flights

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools