Daysync: Tour Manager

Remove the link AND every value the flight filled in — route, times, timezones, airline, duration, all legs and any layovers — leaving an empty flight ready to search again. The title reverts to the placeholder ONLY if it is still the one the lookup wrote; a typed title is kept, so read the returned `name`. DESTRUCTIVE and not reversible; use disconnect_flight to keep the values. The `Airline` and `Flight number` rows go too, unless a human edited them, and the item is left with no legs at all. Notes, tags, reminders and attachments are NOT touched. Safe to repeat.

Mark every schedule item on a day as confirmed. Returns the ids that were previously unconfirmed or had no status, so the change can be undone.

Create an accommodation stay. CAMELCASE ids (tourId/dayId); check-in/out are epoch-millisecond numbers; formatted_address needs geometry.location + geometry.viewport. Audience: `aims` says who it is for; see the field for the rules. Any create ending with NO audience is PUBLIC to the permission ladder and needs the Public permission — that includes `isAdminsOnly`, which is a no-audience create — so a selected-parties editor must name their own scope in `aims`. `visibilityList` still works. `isAdminsOnly` does not round-trip: the item reads back `is_admin_only: false`, and it is visible to you and to anyone with See-everything sight. Returns { id, name }. Safe to retry: repeating this call with the same details within ~10 minutes returns the ORIGINAL record instead of creating a second one — if you get back an id you have already seen, that is what happened. To create a genuine duplicate, pass a new `idempotency_key`.

Create a bulletin on a tour day (dayId only — the tour is resolved from the day). Content field is "body". Returns { bulletin_id }. Notifications: without scheduledFor it is posted at once, its audience sees it in the app, and this call sends no notification for it — hasNotification takes effect only with scheduledFor. With a future scheduledFor it stays hidden until then, and if hasNotification is true Daysync then notifies its audience (in app, plus push/email per their settings), not you. A scheduledFor already in the past is refused (400) when hasNotification is true; with hasNotification false it is posted at once without a notification. Private-account boundary: the connected user's own Daysync tour; no outside service is called on your behalf. Safe to retry: repeating this call with the same details within ~10 minutes returns the ORIGINAL record instead of creating a second one — if you get back an id you have already seen, that is what happened. To create a genuine duplicate, pass a new `idempotency_key`.

Add a person to the organization's key-contact book, then link them to a venue or stay with set_venue_key_contacts / set_stay_key_contacts. Returns { id, ... }. Safe to retry: repeating this call with the same details within ~10 minutes returns the ORIGINAL record instead of creating a second one — if you get back an id you have already seen, that is what happened. To create a genuine duplicate, pass a new `idempotency_key`.

Create an open role — a seat on the roster with nobody in it, so counts, coverage and aims are right before the hire lands. A seat carries places in the structure and NO access whatsoever: whoever fills it starts at own/none with every toggle off. Repeating this call creates a second seat.

Create a guest-list pass type on a tour. day_ids are the days it applies to. Audience: `aims` says who it is for; see the field for the rules. Any create ending with NO audience is PUBLIC to the permission ladder and needs the Public permission — that includes `isAdminOnly` (note the singular), which is a no-audience create — so a selected-parties editor must name their own scope in `aims`. `visibilityList` still works. `isAdminOnly` (note the singular) does not round-trip: the item reads back `is_admin_only: false`, and it is visible to you and to anyone with See-everything sight. Permission: an org admin, or a tour member whose editMode is not `none` and who holds the `guests` permission (`public` for a no-audience create, as above). Returns { id }. Private-account boundary: a pass type is a guest-list category (such as AAA or Guest) on a tour in the connected user's own Daysync account — no ticket is issued, sold or printed, no ticketing or other outside service is called on your behalf, and no notification is sent. Safe to retry: repeating this call with the same details within ~10 minutes returns the ORIGINAL record instead of creating a second one — if you get back an id you have already seen, that is what happened. To create a genuine duplicate, pass a new `idempotency_key`.

Add a room to a stay. roomType comes from list_reference_types (hotelRoomTypes); dates and times are epoch milliseconds. generalNotes and confirmationNumber are required by the API — pass "" if empty. Returns { id, name }. Private-account boundary: it writes a room record on a stay in the connected user's own Daysync account — no hotel booking or reservation is made and no booking or other outside service is called on your behalf. Notifications: unless `hasNotification` is false, Daysync sends a room-assignment notification (in app, plus push/email per their settings) to everyone who can see this stay — org admins included, and occupants unless the stay is sealed without naming them — but not to you; an unchanged retry within the idempotency window does not send it again. Send hasNotification: false to suppress it. Safe to retry: repeating this call with the same details within ~10 minutes returns the ORIGINAL record instead of creating a second one — if you get back an id you have already seen, that is what happened. To create a genuine duplicate, pass a new `idempotency_key`.

Create a schedule item on a tour day. Times are HH:mm time-of-day strings (NOT ISO — the date comes from day_id); travel items (type 2–6) require origin. Audience: `aims` says who it is for; see the field for the rules. Any create ending with NO audience is PUBLIC to the permission ladder and needs the Public permission — that includes `isAdminsOnly`, which is a no-audience create — so a selected-parties editor must name their own scope in `aims`. `visibilityList` still works. `isAdminsOnly` does not round-trip: the item reads back `is_admin_only: false`, and it is visible to you and to anyone with See-everything sight. Returns { id, route_stale, route_computed_at } — plus `reminders` with their server-generated ids when the request sent a `reminder` list. Private-account boundary: it writes a schedule entry on a tour in the connected user's own Daysync account. A flight, hotel or transfer item is a record only — nothing is booked, bought or reserved, no booking or other outside service is called on your behalf, and attachment links are stored, not downloaded. Notifications: the create itself sends none; each `reminder` later notifies the people who can see the item (in app, plus push/email per their settings). Safe to retry: repeating this call with the same details within ~10 minutes returns the ORIGINAL record instead of creating a second one — if you get back an id you have already seen, that is what happened. To create a genuine duplicate, pass a new `idempotency_key`.

Create MANY schedule items in one call — use this instead of looping create_schedule_item when adding a set of items. Same body shape per item, `aims` included — each item carries its own audience. Returns { ids } in request order. All or nothing: up to 1,000 items (within the 512 KB request limit) are written in one transaction, so if any item is refused none is created. Private-account boundary: the connected user's own Daysync tour; nothing is booked and no booking or other outside service is called on your behalf. Notifications: the create sends none; `reminder` entries notify later, as on create_schedule_item. Safe to retry unchanged within ~10 minutes (returns the original ids). Safe to retry: repeating this call with the same details within ~10 minutes returns the ORIGINAL record instead of creating a second one — if you get back an id you have already seen, that is what happened. To create a genuine duplicate, pass a new `idempotency_key`.

Create a tag on a tour. colorId is an AvatarColor id — get one from list_reference_types (group "avatarColors"). Returns the new tag. Safe to retry: repeating this call with the same details within ~10 minutes returns the ORIGINAL record instead of creating a second one — if you get back an id you have already seen, that is what happened. To create a genuine duplicate, pass a new `idempotency_key`.

Create a tour with its days (at least one). Needs org_id from list_organizations and day_type_id values from list_day_types. Only org_admin users can create tours. Returns { id } — the new tour's UUID; call list_tours afterwards to get the created day ids. Safe to retry: repeating this call with the same details within ~10 minutes returns the ORIGINAL record instead of creating a second one — if you get back an id you have already seen, that is what happened. To create a genuine duplicate, pass a new `idempotency_key`.

Create a party — the top level of a tour's structure, e.g. "Audio" or "Band". Repeating this call creates a SECOND party with the same name; read get_tour_structure first if you are unsure whether it exists.

Create a split — a cross-cutting group that ignores the party tree, like "Bus A" or "Early flight".

Create a subgroup under a party. A subgroup may hold members from ANY party — joining it gives access to what it is aimed at, and to nothing else its parent party has. Set sharesToParent when items aimed at it should also be visible to the parent party (viewing only, never editing).

Save a vehicle on a tour so drives can be routed for its size, weight and speed. Units are METRIC. lengthM and trailerLengthM are stored but do NOT affect routing — the provider constrains on height, width and weight only. A trailer's height and width DO: the route is constrained by max(vehicle, trailer) for each. maxSpeedKph and avgSpeedKph DO affect the result, applied to the provider's durations afterwards rather than sent to it. Safe to retry: repeating this call with the same details within ~10 minutes returns the ORIGINAL record instead of creating a second one — if you get back an id you have already seen, that is what happened. To create a genuine duplicate, pass a new `idempotency_key`.

Create a venue on a tour day. venueCategoryId is required in practice (1=commercial, 2=private). Audience: `aims` says who it is for; see the field for the rules. Any create ending with NO audience is PUBLIC to the permission ladder and needs the Public permission — that includes `isAdminsOnly`, which is a no-audience create — so a selected-parties editor must name their own scope in `aims`. `visibility_list` still works. `isAdminsOnly` does not round-trip: the item reads back `is_admin_only: false`, and it is visible to you and to anyone with See-everything sight. Returns { id }. Safe to retry: repeating this call with the same details within ~10 minutes returns the ORIGINAL record instead of creating a second one — if you get back an id you have already seen, that is what happened. To create a genuine duplicate, pass a new `idempotency_key`.

Delete an accommodation.

Soft-delete a bulletin.

Delete a guest-list entry.

Soft-delete a pass type. WITHOUT force it is a SAFE CHECK: if any guest still holds this pass, nothing is deleted and the blocking entries come back in data.guestLists. With force:true those allocations are deleted too, and any guest left holding no pass at all is soft-deleted with them. Reversible with restore_pass_type.

Soft-delete a room. Reversible with restore_room.

Delete a schedule item.

Soft-delete a template. Reversible with restore_schedule_template. Schedule items previously created FROM the template are not affected.

Delete a party, subgroup or split. Deleting a party deletes its subgroups — INCLUDING subgroups sitting under other parties — and clears the affected members' memberships; splits survive. Editing lanes and viewing grants pointing at it are removed in the same transaction. Run preview_structure_delete first. aimCascade decides what happens to items aimed at the group: `keep_reach` (the default) replaces the aim with the people it reached at that moment, so nobody's visibility changes; `remove` deletes the aim, and an item left with no aim at all enters AWAITING RE-AIM — visible only to people who can see the whole tour, NOT public, and not visible to its own creator.

Permanently delete a tag. This is a HARD delete — the tag is removed from every schedule item that carries it and cannot be restored. Check get_tag_usage first.

Soft-delete a tour.

Retire a vehicle. Every drive using it switches to Car (default) and is marked for recalculation; the drives themselves are not deleted. Check get_vehicle_usage first to see how many are affected.

Delete a venue.

Get the exact typed input for named operations — the same JSON Schema each one carries in the tool list. On this connection (tools=all) all 151 operations it is authorised for are already advertised as their own tools with these schemas, so you only need this to re-read one. Returns each operation's full description, inputSchema, outputSchema and read/destructive/idempotent flags. Ask for at most 10 at a time.

Disconnect this MCP session from its Daysync account. Use this when `whoami` shows the wrong account: it revokes the current session so your NEXT request prompts you to sign in again — reconnect with the correct account. Does not delete any Daysync data.

Remove the LINK between a flight item and the lookup, KEEPING every value it filled in so a human can edit them. Reversible and safe to repeat. NOT clear_flight: use it when the figures are right but should stop tracking the lookup. The legs survive unchanged — read them with get_flight_legs. The title is not touched at all.

Render one tour day as a PDF day sheet and get a short-lived download URL back. Answers { url, expiresAt, fileName, pageCount, bytes, ignoredIdCount, cached } — the URL expires, so fetch it promptly rather than storing it. Read-only: it creates nothing on the tour and changes no record (the rendered PDF is cached, nothing else is stored), so it is safe to repeat. Start with a preset (FULL, SCHEDULE or MINIMAL) and narrow it with `options` if needed; ids you pass that you cannot see are dropped and reported in ignoredIdCount.

Put an existing organisation member into an open role. They inherit the seat's party, subgroups and splits — and nothing else: they land at sight `own`, edit `none`, no permissions. The previous occupant's names on sealed items do NOT transfer, because a seal names a person and never a seat. Costs no paid seat.

Get one stay in full — including its custom fields, emails/phones/urls and visibility. list_accommodation returns a leaner projection.

Total guests across a day's APPROVED guest-list entries — the number a day's cap is checked against. It is a SUM of party sizes, not a row count, and it is not derivable from a paged get_guest_list.

Get one channel or group chat: name, description, whether it is public/archived, and its member count.

Parties, subgroups, splits and people that could be added to a day's audience, each with how many people it would add.

Read one tour day as a print-ready day sheet MODEL: header, running order, venues, stays, consolidated key contacts, guest-list totals, bulletins and the upcoming-days strip, filtered to what you can see. Use it to decide what to include before calling export_day_sheet; the ids it returns are the ids that tool accepts. For the raw records instead, use get_tour_data.

Who can see a day: mode (public/limited/admins), its audiences, day and tour headcounts, whether you are on it and can manage it, and the dayRevision.