seats.aero MCP server

get_bulk_avail

Read-onlyIdempotent

Retrieve bulk flight availability for a mileage program source. Filter by date range, cabin class, origin, and destination regions to find award seats.

Instructions

Find bulk availability for a particular source.

Input Schema

TableJSON Schema

Name	Required	Description
`skip`	No
`take`	No	Maximum results to return (10-1000; default 500).
`cursor`	No
`source`	Yes	Mileage program source to retrieve.
`endDate`	No	Latest departure date, in YYYY-MM-DD format.
`startDate`	No	Earliest departure date, in YYYY-MM-DD format.
`cabinClass`	No	Only return results with this cabin available.
`originRegion`	No	Only return results originating in this region.
`include_filtered`	No	Include raw results normally removed by dynamic-price filters.
`destinationRegion`	No	Only return results arriving in this region.

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 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: +"Only return results with this cabin available."

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 / destinationRegion / description
```
Added value: +"Only return results arriving in this region."
```

addedInput schema / properties / destinationRegion / enum

Added value: +[
+  "North America",
+  "South America",
+  "Africa",
+  "Asia",
+  "Europe",
+  "Oceania"
+]

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 / originRegion / description

Added value: +"Only return results originating in this region."

addedInput schema / properties / originRegion / enum

Added value: +[
+  "North America",
+  "South America",
+  "Africa",
+  "Asia",
+  "Europe",
+  "Oceania"
+]

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 / source / description

Added value: +"Mileage program source to retrieve."

changedInput schema / properties / source / enum

Previous value: -[
-  "eurobonus",
-  "virginatlantic",
-  "aeromexico",
-  "american",
-  "delta",
-  "etihad",
-  "united",
-  "emirates",
-  "aeroplan",
-  "alaska",
-  "velocity",
-  "qantas",
-  "connectmiles",
-  "azul",
-  "smiles",
-  "flyingblue",
-  "jetblue",
-  "qatar",
-  "turkish",
-  "singapore",
-  "ethiopian",
-  "saudia"
-]New value: +[
+  "eurobonus",
+  "virginatlantic",
+  "aeromexico",
+  "american",
+  "delta",
+  "etihad",
+  "united",
+  "emirates",
+  "aeroplan",
+  "alaska",
+  "velocity",
+  "qantas",
+  "connectmiles",
+  "azul",
+  "smiles",
+  "flyingblue",
+  "jetblue",
+  "qatar",
+  "turkish",
+  "singapore",
+  "ethiopian",
+  "saudia",
+  "finnair",
+  "lufthansa",
+  "frontier",
+  "spirit"
+]

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

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, indicating a safe, non-mutating operation. The description adds no behavioral details such as pagination, rate limits, or result completeness, but it also does not contradict the annotations. The annotations carry the transparency burden, so the score is adequate but not enhanced.

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?

The description is a single sentence with no redundant words, front-loading the action. However, it is so brief that it verges on under-specification; it could have added useful context while remaining concise.

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?

The tool has 10 parameters, no output schema, and complex sibling tools. The description 'Find bulk availability for a particular source' is too thin to explain what 'bulk availability' means, what the response contains, or how to construct a query. Significant gaps remain for an agent to use the tool correctly.

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 coverage is 80%, with detailed descriptions for most parameters, so the baseline is 3. The description only adds marginal meaning by implying the 'source' parameter is the key filter ('for a particular source'), but it offers no additional syntax or contextual detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Find' and resource 'bulk availability' scoped to 'a particular source,' which helps distinguish it from sibling tools like get_flights or get_destinations. However, it does not clarify what 'bulk availability' means (e.g., multi-date or multi-route results), leaving some ambiguity about the tool's exact function.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like live_search or get_flights. There is no mention of use cases, prerequisites, or exclusions, leaving the agent without context for tool selection.

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

Deploy Server

get_bulk_avail

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools