Mixmax

Read your phone/dialer calls placed with the Mixmax Dialer (Twilio) — NOT meeting recordings; use the meetings tool (get_meeting_transcript) for those. Read-only, and strictly your own calls. Actions: - list_calls: your dialed calls, newest first. Filter with hasRecording (true/false). Results come in pages of at most 25 rows: when a response has hasNext: true, call again with next set to the returned cursor, verbatim; judge the end by hasNext, never by row count, and never invent a cursor. - get_call: one call's metadata (timing, outcome, duration, numbers, CRM linkage, whether a recording exists) by callId from a list_calls row. - get_call_transcript: the diarized transcript (speaker turns: name, message, timestamp) for a call by callId, sliced with skip/limit (default 100, max 200 turns per page); judge the end by pagination.hasMore. A transcript may still be generating (queued — retry shortly) and transcripts are retained for 30 days.

calls_read

Activate the recipients from the activation review currently shown in the Mixmax card. The card calls this tool after the user presses Activate. It revalidates the review and refuses if recipients, capacity, or timing changed.

confirm_sequence_activation

Read the Mixmax Live Feed — real-time tracked-email engagement activity. Read-only. Actions: - get_live_feed: List recent engagement activity across your tracked emails. Filter with a live-feed search string (query), e.g. "opened:last7days from:acme.com". Use this to answer "who engaged recently" / "what happened with my outreach". - get_message_events: Get the chronological engagement timeline (opens, clicks, replies) for a single message (messageId) OR for a contact (contactEmail). Exactly one of the two is required. Paging (both actions): results come in pages of at most 25 rows. When a response has hasNext: true, call the same action again with next set to the returned cursor. Judge the end by hasNext, never by row count: a full page can be the last one, and the last get_message_events page can be empty. Stop only when hasNext is false. The feed is live: a row that gets new engagement after you have passed it moves to the top of the feed and is not revisited by the current walk, so each page reflects activity as of that call. If you re-walk from the start, dedupe by messageId. get_live_feed returns stats on the first page only; they describe the whole query, not the page (stats.sent is the total number of matching messages). Keep the default limit of 25 and narrow long walks with a dated query such as "sent:last30days". If a call times out or fails with retryable: true, retry the same cursor at most once, then report the error. Never restart from page 1 and never invent a cursor.

live_feed

Query Mixmax meetings and calendar data. Actions: get_event, search_events, find_event_by_meet_id, get_calendar, get_meeting_prep, list_meeting_preps, get_meeting_summary, search_meeting_summaries, get_meeting_transcript, get_meeting_assistant_settings, list_meeting_types, get_booking_links, get_admin_copilot_settings. get_booking_links returns the user's Mixmax calendar booking links: their calendar URL plus one URL per meeting template (name, duration, isDefault) — use it when writing emails or sequence steps that invite the recipient to book a meeting, instead of guessing or hardcoding a URL. Pick the template that matches the meeting being offered, or the isDefault one when none is specified.

meetings

Send, schedule, list, and cancel emails as the authenticated Mixmax seller, with open/link/file tracking ON by default. Actions: send (now); schedule (future — pass scheduledAt as ISO-8601 with a timezone offset, e.g. 2026-06-10T09:00:00-07:00); list_scheduled (your not-yet-sent scheduled emails); unschedule (cancel one by messageId from a prior list_scheduled). send/schedule send a REAL email — not a draft. Optionally attach an interactive poll (clickable multiple-choice) to a send/schedule via the `poll` param. Disable a tracking kind via trackingEnabled / linkTrackingEnabled / fileTrackingEnabled = false. To read inbox threads/messages, use the read-only emails surface.

messages

Get information about Mixmax

mixmax_info

List the authenticated Mixmax seller's ACTIVE follow-up reminders. Read-only. Action: - list_reminders: list your upcoming reminders. Each row has reminderId (pass it to edit_reminder / delete_reminder), contact (the recipients), subject (thread subject), triggerType (noReply | notRead | regardless), and scheduledDate (ISO-8601, when it fires). Paginated via limit + next. Scope: ACTIVE / upcoming reminders only — those still scheduled to fire. It EXCLUDES reminders that have already fired or been cancelled/completed, and excludes AI smart-followups. Owner-only: you only ever see your OWN reminders. Pagination: an empty results page can still return a "next" cursor — keep paging with it; an empty page does NOT mean you have no reminders.

list_reminders

Create, edit, and delete the authenticated Mixmax seller's OWN follow-up reminders. Actions: - create_reminder: schedule a follow-up reminder on an email thread. Required: trigger (noReply | notRead | regardless), date (epoch milliseconds, in the future), service (gmail | outlook), and at least one of serviceThreadId / serviceMessageId / mixmaxMessageId. notRead REQUIRES mixmaxMessageId. Optional: threadSubject, description, archiveThread. Returns the created reminder including its reminderId (use it to edit_reminder / delete_reminder). - edit_reminder: change an UPCOMING reminder by reminderId. Editable: date, description. (If the reminder has already fired or been dismissed, nothing changes.) - delete_reminder: permanently remove an upcoming reminder by reminderId. DESTRUCTIVE and irreversible (no undo). Owner-only: you can only manage your OWN reminders. create is at-least-once (no idempotency) — if a create times out, do NOT retry blindly; verify with list_reminders. Get a reminderId from list_reminders.

reminders_write

Review how pending recipients will be distributed across sending days before activating a Mixmax sequence. Shows daily capacity already used by other sequences, weekend/holiday blocks, and recipients held by the monthly limit. This call never activates recipients. Use it before every activation.

preview_sequence_activation

Assess the saved email content in a Mixmax sequence for deliverability risks. The first call queues an asynchronous assessment. If it returns queued or running, wait briefly and call again with the returned assessmentId. Returns a narrative plus structured findings attributed to sequence stages and A/B variants.

assess_sequence_deliverability