create_trip
ChatGPTUse this when starting a brand-new trip. Pass blocks to set the full itinerary in one call — strongly preferred. For an EXISTING trip, use replace_itinerary (not create_trip) to swap out the schedule.
Overview
TripHelm turns trip planning into a real calendar instead of a tangle of notes, tabs, and screenshots. Describe your trip in plain language and TripHelm lays it out for you — flights, meals, check-ins, activities, and downtime, each placed on the right day at the right time. Need to change something? Just say it: "push dinner to 8," "add a coffee stop before the museum," "lighten up day 3" — and the schedule updates. Everything saves to your TripHelm account and opens in the full web app, where you can drag, drop, and fine-tune any block by hand. Plan a whole trip from scratch or adjust one already underway. Either way you walk away with a clear, hour-by-hour schedule you can actually follow — not a wall of text you're re-reading at the gate.
Tools
delete_trip
ChatGPTUse this only when the user explicitly asks to delete a trip. Permanently removes the trip and all its blocks. Irreversible — confirm with the user first if the request is ambiguous.
edit_blocks
ChatGPTUse this for ALL granular block edits on an existing trip — adding, changing, and removing blocks, in any combination, applied atomically in one call (removals first, then updates, then adds). When the user asks to add or change something — a restaurant, an activity, a time — call this and actually write it; don't just list suggestions in chat. Call get_trip_data first for current state and blockIds. If a new item supersedes a generic placeholder (e.g. a named restaurant for an existing 'Dinner' slot), pass the placeholder's id in
remove and the new block in add — one atomic call, no overlapping duplicate. Adds/updates are all-or-nothing: one invalid item rejects the whole call (with a message naming it) and nothing is written. Overlap is allowed and often intentional (concurrent options, a busy stretch) — overlapping blocks are written and reported per block, never rejected. Times are minutes from midnight, 0–1440; split a midnight-crossing block across day N and N+1. For a brand-new trip use create_trip with blocks[]; to rewrite a whole day or the whole trip use replace_itinerary.get_trip
ChatGPTUse this to SHOW a trip — on clients that support MCP Apps it renders the trip's interactive calendar in chat. Call it when the user asks to see the trip, a day, or 'the calendar'; never recite an itinerary from memory (your copy may be stale). For data-only reads — freshness checks before edits, looking up block IDs, internal reasoning — use get_trip_data instead: same data, nothing rendered in chat.
get_trip_data
ChatGPTUse this to read a trip's full data — title, dates, and every block with its blockId — WITHOUT rendering anything in chat. ALWAYS call this immediately before any edit operation — the user may have edited the trip in the Trip Helm web app since you last looked, and block IDs change whenever replace_itinerary rewrites the trip or a day. You'll need the block IDs from here for edit_blocks. To SHOW the trip to the user, use get_trip instead.
list_trips
ChatGPTUse this when the user wants to see, browse, or filter their existing trips. Optionally filter to trips updated after a given date. On clients that support MCP Apps, this call renders an interactive trip browser in chat — prefer calling it over listing trips from memory.
replace_itinerary
ChatGPTUse this to rewrite the schedule wholesale. Without dayIndex it replans the WHOLE trip — wipes ALL existing blocks and replaces them with the new array. With dayIndex it restructures that single day only — wipes just that day's blocks and replaces them (pass an empty blocks array to clear the day); every block's dayIndex must equal the dayIndex parameter. ALWAYS call get_trip_data immediately before this; the user may have edited the trip in the Trip Helm web app, and this wipe-and-replace assigns NEW block IDs. For surgical changes to individual blocks, use edit_blocks instead.
search_blocks
ChatGPTUse this when the user asks about something specific across all their trips without naming the trip — e.g. 'find that yakitori place', 'when was my flight to Tokyo?', or 'all my confirmed dinner reservations'. Matches block titles and body text; optional kind/status filters narrow the results (kind 'meal' + status 'confirmed' = restaurant reservations).
update_trip
ChatGPTUse this to change trip-level fields: title, destination, dates, or the trip-level metadata bag. Does NOT touch blocks — to edit blocks, use edit_blocks or replace_itinerary.
Capabilities
InteractiveWrites
Example Prompts
Click any prompt to copy it.
