Plan a SEA / Seattle trip
plan_tripCreates a trip plan for a trip through Seattle-Tacoma Airport (SEA) or Seattle: rides, hotel, flights, a cruise from Seattle, tours and events in one plan, timed so it fits. Give the arrival date (or a cruise sailing), travelers, and anything already known; you can add the rest later with add_to_plan. Creates a stored plan and returns plan_id, edit_key (keep private; needed to change it), plan_url (the visual, shareable plan page: show this to the traveler), summary_markdown, what's still needed, warnings, and hotel_options. The rides between the airport, hotel, pier and stops are planned automatically. Nothing is booked or charged: the traveler books from plan_url.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "plan_trip"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | The day they leave (no cruise), YYYY-MM-DD. Or give nights. | |
| kids | No | How many of them are kids (default 0). | |
| items | No | More to put on the plan right away (up to 12), each like add_to_plan's item, e.g. {"type":"tour","id":"space-needle","date":"2027-05-05"}. | |
| start | No | The day they arrive in Seattle, YYYY-MM-DD. Optional with a cruise (default: the day before sailing). | |
| nights | No | Nights in Seattle instead of end (0-21, default 2). With a cruise the Seattle nights run to sailing day. | |
| purpose | No | vacation (default), business, visit, event or other. | |
| travelers | No | Everyone traveling (1-14, default 2). | |
| hotel_name | No | hotel: or a hotel booked elsewhere, "name, address". | |
| hotel_slug | No | One of our hotels (slug from hotel_options of an earlier answer, or recommend_hotels_with_rides). | |
| cruise_ship | No | A cruise from Seattle: the ship (from find_cruise_sailings). | |
| home_airport | No | flight: 3-letter code they fly from, e.g. ORD. | |
| landing_time | No | flight: landing at SEA, Seattle time HH:MM. | |
| return_flight | No | flight: flight home, e.g. AS 38. | |
| arrival_flight | No | flight: arriving flight number, e.g. AS 23, only once booked (the plan then shows the flight in as booked). Before that give landing_time, or search_flights. | |
| departure_time | No | flight: flight home's departure, Seattle time HH:MM. | |
| cruise_sail_date | No | The sailing date in Seattle, YYYY-MM-DD. | |
| cruise_already_booked | No | They already booked the cruise. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | The plan's name, e.g. "Alaska cruise · May 7–14": use it when the traveler has more than one plan. | |
| plan_id | Yes | ||
| edit_key | Yes | ||
| plan_url | Yes | The visual plan page for the traveler. Share this link. | |
| summary_markdown | No | A short day-by-day summary to show in the chat. | |
| traveler_edit_url | No |