Skip to main content
Glama

search_change_flights

Search alternative flights for an existing reservation and view pricing differences, including credits or additional payment due.

Instructions

Search alternative flights for an existing reservation (the "change flight" flow).

Returns the full reshop payload: a ±6-day price carousel around departure_date, plus up to 40 flight options with per-cabin pricing (flightCells contain fare, netPrice = delta vs paid, cabinType, fareType, changeType, seatsLeft).

The endpoint allows changing origin city, destination city, and date in a single query — AA validates against the original fare rules and either returns SUCCESS or an error. Negative netPrice means you'd be issued a travel credit; positive means additional payment due. Change fees are usually $0 (waived on non-Basic- Economy fares).

PRICING SCOPE: All numbers are TOTAL for every passenger on the PNR. This endpoint does not support per-passenger pricing. To change only some passengers on a multi-pax booking, the PNR typically has to be split first via an agent (the divideEligible flag on the reservation indicates whether the self-serve split is allowed; partial reshop without a split usually requires a phone agent).

Args: record_locator: 6-character PNR (e.g., "UHJHHT"). last_name: Lead passenger last name. first_name: Lead passenger first name. departure_date: New departure date (YYYY-MM-DD). origin_airport: New origin airport (3-letter IATA — can differ from original). destination_airport: New destination airport (3-letter IATA — can differ from original). slice_index: Which slice of the reservation to change (0 = first; matters for round-trips). carousel_days: Include the ±6-day min-price grid in the response (default True). account: Account name (optional, uses default).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
record_locatorYes
last_nameYes
first_nameYes
departure_dateYes
origin_airportYes
destination_airportYes
slice_indexNo
carousel_daysNo
accountNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. Describes return payload structure and pricing behavior. Does not explicitly state that this is a pure search (read-only) operation, which could cause ambiguity about side effects.

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?

Well-structured with high-level purpose first, then detailed return description, warnings, and parameter list. Slightly long but each section adds necessary information. Concise for the complexity.

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?

Given 9 parameters, no annotations, and output schema existence, the description covers return format, pricing details, split PNR caveats, and parameter explanations thoroughly. Leaves minimal gaps for agent understanding.

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?

Despite 0% schema coverage, the 'Args' section explains each parameter with format and constraints (e.g., 6-character PNR, YYYY-MM-DD for dates, meaning of slice_index and carousel_days). Adds significant value beyond schema.

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?

Clearly states 'search alternative flights for an existing reservation (the 'change flight' flow)', with specific verb and resource. Distinguished from sibling tools like get_reservation_by_locator which is about viewing reservations, not changing.

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?

Explains when to use for change flight flow, gives context on pricing scope and PNR splitting. Does not explicitly state when not to use, but provides enough context with alternatives like needing an agent for partial changes.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thehesiod/aa-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server