Apptoto

List the authenticated user's booking pages. Returns id, name, public url, enabled flag, appointment types, and field definitions for each page. 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 calendar events for the authenticated user within a date range. Use ISO 8601 timestamps (e.g. "2026-05-20T00:00:00Z"). Results are paginated; default 20 per page, max 50.

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: Start a new conversation by sending a message using an approved template. 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_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.

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.