Find Destination

Surface inspiration when a user knows where they want to leave from but not where they want to go. Typical prompts include “cheap beach getaways from New York” or “weekend trips out of London under €200”. Results come back ranked by lowest available fare so the user can compare options before committing to a route.

Tool description (what the LLM sees)

Discover travel destinations accessible from your departure airports.

Search globally or restrict results with the destinations list of IATA airport/city codes. For a region or theme, supply the relevant destination codes; there is no region parameter. Returns destinations sorted by cheapest available flight.

ORIGINS: Use 3-letter IATA airport codes (CDG, JFK) or city codes (PAR, NYC). When listing airports, include the nearby airports the user can use (e.g., CDG + ORY for Paris). A code that names a multi-airport city covers every airport of that city; any other code is that one airport. LAX, MIA and LAS are both a city code and that city's main airport, so they are read as the city here.

Next step: Use flight_calendar with the destination to get specific flights with offer_tokens for pricing.

The result carries `search_criteria` (what was actually searched) and, on a non-empty answer, `next`: the `flight_calendar` calls for the best destinations. Follow `next` to price a destination; on an empty answer the `message` names the window that was searched.

Every price this tool returns is one adult's cached fare (search_criteria.priced_for: "one_adult"); the tool takes no party. To price the whole party, price-check the offer using flight_search with price_check and the travellers' counts in traveler_counts.

Parameters

Name	Type	Required	Description
`origins`	`array<string>`	Yes	Origin airport IATA codes or city codes (3 letters). Include all nearby airports. Examples: [“JFK”, “LGA”, “EWR”] for NYC. A code that names a multi-airport city (NYC, LON, PAR, and LAX, MIA, LAS, which a city shares with its main airport) covers every airport of that city; any other code is that one airport.
`destinations`	`array<string>`	No	Filter to specific destination IATA codes. Omit for global discovery mode.
`trip_type`	`enum ("oneway" \| "roundtrip")`	Yes	Trip type: “oneway” or “roundtrip”.
`departure_dates`	`array<string>`	No	Specific departure dates (YYYY-MM-DD). Multiple dates searched with OR logic.
`departure_date_ranges`	`array<object>`	No	Departure date ranges for flexible search.
`departure_date_ranges[].start`	`string`	Yes	Range start date (YYYY-MM-DD)
`departure_date_ranges[].end`	`string`	Yes	Range end date (YYYY-MM-DD)
`return_dates`	`array<unknown> \| null`	No	Specific return dates (YYYY-MM-DD) for round-trip flights.
`return_date_ranges`	`array<object> \| null`	No	Return date ranges for flexible round-trip search.
`stay_days`	`integer \| null`	No	Exact stay duration in days for round trips. Omit when trip_type is “oneway”.
`stay_days_range`	`object \| null`	No	Flexible stay duration range for round trips. Example: {min: 5, max: 10}. Omit when trip_type is “oneway”.
`direct_only`	`boolean`	No	Only return nonstop flights.
`cabin_class`	`enum ("economy" \| "premium_economy" \| "business" \| "first") \| null`	No	Cabin class filter.
`max_total`	`number \| null`	No	Maximum total of the cached fare, in the requested currency. Cached fares are priced for one adult, so the cap applies to a one-adult fare. For a whole-party budget, divide it by the number of ADULTS only and treat the result as a loose pre-filter: children and lap infants usually cost less than an adult, so dividing by every traveller would exclude affordable trips. Send a per-person budget as-is. The exact whole-trip budget check is flight_search with max_total.
`sort_by`	`enum ("lowest" \| "recommendation")`	No	Sort order. Default: “lowest” (cheapest first).
`limit`	`integer`	No	Max destinations to return per page (1-100). Default 20.
`offset`	`integer`	No	Number of destinations to skip, for pagination. Default 0.
`currency`	`string`	No	ISO 4217 currency code. Defaults to “USD”.
`locale`	`string`	No	BCP 47 locale. Defaults to “en-US”.
`format`	`enum ("text" \| "json")`	No	Compatibility option: “text” and “json” both return JSON in the text channel for successful or empty results. Read structuredContent for the result data.
`user_intent`	`string`	No	The end user’s current request in their own words, e.g. “help me with my travel plans”. Pass it as-is when short; otherwise condense the goal and constraints into 1-2 sentences. Strip personal identifiers (names, emails, phone numbers, addresses, payment details), replace them with placeholders like “[name]”. Optional. Jinko uses it to understand demand, and hotel_search uses it to rank hotel results against what the user asked for (e.g. “quiet, with a gym, near Times Square”), so keep the user’s stated preferences in it.

Examples

Explore destinations under $500 from New York in June:

{
  "name": "find_destination",
  "arguments": {
    "origins": ["JFK", "LGA", "EWR"],
    "trip_type": "roundtrip",
    "departure_date_ranges": [{ "start": "2027-06-01", "end": "2027-06-30" }],
    "stay_days_range": { "min": 5, "max": 10 },
    "max_total": 500,
    "currency": "USD"
  }
}

Europe from Paris in spring, direct only:

{
  "name": "find_destination",
  "arguments": {
    "origins": ["CDG", "ORY"],
    "destinations": ["LHR", "AMS", "FRA", "MAD", "BCN", "ROM"],
    "trip_type": "roundtrip",
    "departure_date_ranges": [{ "start": "2027-04-01", "end": "2027-05-31" }],
    "stay_days": 3,
    "direct_only": true,
    "currency": "EUR"
  }
}

Read destination summaries from the MCP result’s structuredContent.destinations[]. A destination’s cached candidate token is offer_token. On a non-empty result, structuredContent.next suggests flight_calendar calls for up to the first three destinations. If the chosen destination is among them, pass its matching next.args entry to flight_calendar. Read the calendar response’s structuredContent.next.args for the live-pricing handoff:

When cached fares are found, choose a candidate and send its price_check object as the flight_search input’s price_check.
When the calendar is empty, each suggested entry instead contains search and traveler_counts; pass a chosen entry as the flight_search input.

Use live pricing before quoting or booking.

Introduction

Flights

Hotels

Cars

Trip & Payment

Marketing claim

Parameters

Examples

​Parameters

​Examples

Parameters

Examples