Create an itinerary link for the Meridian Dispatch app
create_itinerary_linkGenerate an itinerary import link: turn a day-by-day travel itinerary into a shareable "Add Itinerary to Meridian Dispatch" link. Use it only when the traveller wants a link to share or open elsewhere. To save a trip to the traveller's own account, privately, use create_plan (or edit_plan for one they have): that needs no link and can be deleted. To draft the plan itself, use get_destination, get_dispatch and get_place first and link places with their meridiandispatch.com URLs; for a trip the traveller will take themselves, read get_travel_preferences first (it needs sign-in) and fit the hotels, pace and routing to it. Opening the link on an iPhone with the Meridian Dispatch app shows the trip and adds it to the Plan tab as a new plan, after the traveller picks the first day; anywhere else it opens a web preview of the days. Days are numbered (day 1, 2, 3) or dated, and every day needs a hotel stay or its own city. A dated link opens on its dates, which the traveller can still move. When the dates are not negotiable (a trip built around a festival, a match, a concert or any event on fixed days), date every day and set fixed_dates: the app then adds the trip on exactly those dates with no date picker, and the link's page tells the traveller so. A place given with its meridiandispatch.com page URL arrives with that page's field record. Each call creates a new, public, permanent link that cannot be deleted (not idempotent). Anyone with it sees the trip's dates, towns, stops and hotel names; booking references, emails and phone numbers are removed. Tell the traveller this before making one. Returns the link, ready-made markdown, counts of days and items, and the places matched and not matched to the guides. An invalid itinerary returns an error listing every problem; too many links in an hour returns a rate-limit error.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"title": "<title>",
"country_code": "<country_code>",
"days": "<days>"
},
"name": "create_itinerary_link"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| car | No | A rental car the trip needs (a road trip, or days in the countryside). The app adds it as a car rental still to book and draws those days' travel as driving. from_day and to_day are day numbers on both numbered and dated itineraries; to_day may be the morning after the last day. Picked up and returned at airport and airport_home unless pickup or dropoff name other airports. | |
| days | Yes | The days in order, each with what to do. Number every day or date every day, not a mix. Every day needs its own city or a stay (in stays) whose check-in to check-out, inclusive, covers it; the error names each day with neither. | |
| stays | No | Where the traveller sleeps, by hotel name. Optional: a day not between a stay's check-in and check-out (inclusive) must give its own city, which places it in the app until a hotel is added. check_in_day and check_out_day on a numbered itinerary, check_in and check_out (YYYY-MM-DD) on a dated one. | |
| title | Yes | The trip, e.g. "Six days on the Montenegro coast". | |
| airport | No | IATA code of the airport to fly into, e.g. "GDN". The app books the flight in to it on day 1 instead of guessing (a country's busiest airport is often the wrong one: Warsaw for Gdańsk). | |
| summary | No | One short paragraph shown under the title: what the trip is and why it works. | |
| fixed_dates | No | true when the trip only works on its dates, e.g. it is built around an event. Needs a date on every day (not day numbers). The app imports it on those dates and the traveller cannot move them. Leave out for a trip that works any time. | |
| airport_home | No | IATA code of the airport to fly home from, when it differs from airport. | |
| country_code | Yes | ISO 3166 alpha-2 code of the main country, e.g. "ME". |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | The link to give the traveller. | |
| days | No | ||
| dated | No | ||
| items | No | ||
| opens | No | ||
| title | No | ||
| markdown | No | ||
| link_text | No | ||
| fixed_dates | No | ||
| unmatched_places | No | Places that matched nothing in the guides; resend with the proper name to attach a location. | |
| places_matched_to_guides | No |