Apptoto

List the address books (contact sources) connected to this Apptoto account.

List the authenticated user's booking pages. Returns id, name, public url, enabled flag, appointment types, and field definitions for each page. A page's `url` is its shareable public booking link. Inside an appointment type, `link_to_url` is NOT a separate booking link for that type -- it only appears on types whose `action` is "link", meaning picking that type forwards the visitor to another one of the user's booking pages, and that other page is listed here in its own right. There is no per-appointment-type link: to send someone to a specific type, share the page `url`. Paginated; default 20 per page, max 50.

List completed bookings (self-scheduled appointments) made through a booking page within a date range. Paginated; default 20 per page, max 50.

List the calendars connected to this Apptoto account. Returns id, title, type (google/outlook/etc.), and enabled state for each.

List or search contacts in the user's address books. Paginated; default 20 per page, max 50.

Fetch the individual messages (logs) for one conversation. Supply the conversation_id from list_conversations. Returns each message with content, from, to, direction, delivery state, and timestamps.

List the message templates that can be used to start a conversation with start_conversation. Only approved templates are returned (any template awaiting content approval is omitted). Each template includes: id - pass this as template_id to start_conversation name - human-readable template name comm_types - which channels the template supports: { sms, email, call } (call means a voice call) Use the comm_types to decide the `type` to pass to start_conversation.

List conversations (text/email/call threads) for the authenticated user. Defaults to the inbox folder. The optional `q` parameter accepts the Apptoto search syntax: from:[email protected] - match sender to=+15035551212 - exact phone match (= is exact, : is tokenized) comm_type:sms - only SMS conversations event:sent AND delivery_state:delivered auto:true - only automated messages subject:"appointment confirmation" content:reschedule - body text match confirmed:true - participant confirmed the appointment For the full search syntax reference (additional operators, aggregations, fuzzy matching) see https://www.apptoto.com/apptoto-manual/article/inbox-outbox-tab/conversation-search-syntax/ Returns id, event, participant, conversation_type, from, to, last_out, last_in for each conversation. Paginated; default 20 per page, max 50.

List or search the authenticated user's calendar events (appointments) within a date range. Events can be ANYTHING on the user's connected calendars -- flights and travel, doctor/dentist appointments, meetings, closings, reminders, personal plans -- so a question about the user's own flights, trips, appointments, or "what's coming up" is almost always answerable here, not out of scope. For "my next/upcoming X" (e.g. "upcoming flights"), set q to the keyword (e.g. "flight") and begin to the current time, then take the soonest result. q supports a real query language (see its description) -- when the user names SEVERAL people or topics, combine them into ONE call with "or" rather than making a separate call per name. Results are paginated (default 20 per page, max 50); each response's "total" counts every match, not just this page, so use it to decide whether to fetch more pages. A "warnings" key means the search understood part of your query but not all of it; read it and retry rather than reporting no results. Each event includes created_on_calendar / updated_on_calendar timestamps, so "when was this appointment created/booked" is answerable here. Each participant carries that person's REAL, shareable links: `link` is their Appointment Page -- the page a message's {{ reminder.link }} field points at, where they see their appointment details and can confirm, cancel, reschedule, or add it to their calendar -- along with `reschedule_link`, `direct_reschedule_link` and `cancel_link`. These are live URLs, safe to show the user. This is the ONLY way to get a real link for a real appointment: preview_message_template always renders a fixed .../r/preview placeholder instead. What that page shows -- whether it carries the address, a map, directions -- is this account's own Appointment Page setup: read it with get_appointment_page / preview_appointment_page, never from memory. Each participant also says how and when they got onto the appointment: `manually_added` is true when someone added that person in Apptoto by hand (or edited their name/phone/email there), false when Apptoto read them from the calendar entry; `added_at` is when they were added. When the same person appears more than once on an appointment, compare these instead of guessing whether a sync or a person put the extra one there.

List the automated reminder messages from a participant's applicable schedule. Use get_event / list_conversations to find a participant_id first. Each message returns id, name, comm_type (sms/call/email), content, enabled, and -- evaluated for this participant -- matches (whether the message applies), send_time (when it would fire), queued (whether it is currently scheduled to send), and reminder_state. Use schedule_participant_auto_message / cancel_participant_auto_message to queue or un-queue one for its configured time, or send_participant_auto_message to send it immediately.

Marks all participants in an event with a state (e.g. confirmed, cancelled, noshow). Supply either `id` or `external_id` to identify the event. Use list_events / get_event to find the event first. WRITE: this updates participant state and may trigger redispatch of reminders.

Report a problem you ran into, or a capability the user asked for that the available Apptoto MCP tools do not support. Use this when a task cannot be completed with the current tools, when a tool behaves unexpectedly, or when the user explicitly asks to leave feedback. Describe who the user is, what they were trying to do, what the issue or limitation is, and what change would help. This sends a report to the Apptoto team.

WRITE: Send a reply on an existing conversation. This SENDS a real SMS or email and may incur per-message cost on the user's account. Always confirm with the user before calling. Supply conversation_id (from list_conversations) and the message body.

WRITE: Queue one of a participant's automated reminder messages so it sends automatically at its configured time (not immediately). Use this to "enable" a specific auto message for a participant. Call list_participant_auto_messages first to get the participant_id and the auto_message_id. The message must have an applicable send_time for this participant. To send immediately instead, use send_participant_auto_message. To un-queue, use cancel_participant_auto_message.

WRITE: Send one of a participant's automated reminder messages RIGHT NOW, mirroring the "send now" button in the participant schedule editor. This SENDS a real SMS, email, or voice call and may incur per-message cost on the user's account. Always confirm with the user before calling. Call list_participant_auto_messages first to get the participant_id and the auto_message_id to send. To queue a message for its configured time instead of sending immediately, use schedule_participant_auto_message.

WRITE: Message the participant(s) of an appointment (or any phone/email) by sending an approved template as a new SMS, email, or voice call. Use this to notify people about their appointment -- e.g. that it was rescheduled, confirmed, or cancelled. This SENDS a real message and may incur per-message cost on the user's account. Always confirm with the user before calling. Call list_conversation_templates first to get a template_id and the channels (comm_types) it supports. Choose the recipient by supplying exactly ONE of: participant_id - a specific participant on an event (use list_conversations / get_event to find ids) event_id - every participant on the event receives the message individually to - a one-off phone number (sms/call) or email address (email) When using `to`, set `type` to match: "sms" or "call" for a phone number, "email" for an email address. This tool only sends pre-approved templates. For free-text (non-template) wording, use send_message_to_participant instead.

Add or remove a tag on an event, participant, or contact. The tag is appended to the title for events and tracked in a searchable tags field for all targets. Identify the target with `id` (or `external_id` for events and contacts; participants require `id`). Set `remove` to true to remove the tag instead of adding it. WRITE: requires events:write for event/participant targets, contacts:write for contact targets.

Updates an existing contact. Supply either `id` (Apptoto contact id) or `external_id` to identify the contact. Only the fields supplied are changed. Phone numbers and email addresses are managed explicitly: use `add_phone` / `remove_phone` to add or remove a single value, or pass `phone_numbers` (array of strings) to replace the entire set. Same for `add_email` / `remove_email` / `email_addresses`. Use `primary_phone` / `primary_email` to mark which existing value is the primary (the one returned as the contact's main phone/email); pair with `add_phone` in the same call to add and promote in one step. To change a phone, remove the old one and add the new one. WRITE: this modifies an existing contact.

Updates an existing event. Supply either `id` (Apptoto event id) or `external_id` to identify it. Only fields supplied are changed. WRITE: this modifies a real calendar event.