Front

List the company's available ticket statuses, each a status a conversation can be set to via update_conversation_status. Returns an empty list when ticketing is not enabled for the company.

list_statuses

List tags in the workspace.

list_tags

List teammates in the workspace.

list_teammates

List teams in the workspace.

list_teams

Move a conversation to a different inbox. Replaces the conversation's current inbox association with the destination inbox — this is not additive. Provide the destination inbox ID (inb_xxx) from list_inboxes.

move_conversation

Read an account (company) record.

read_account

Read a contact record.

read_contact

Read a conversation: its messages and their IDs, comments, and activity entries, as a paginated, newest-first timeline under `entries`, plus its header (subject, status, isClosed, assigneeId, assigneeName, assigneeAlias, inboxes (each with id and name), tagIds, ticketIds, ticketStatus, scheduledReminders, updatedAt). Pass `entries.nextCursor` back as `cursor` to fetch older entries, and stop when `entries.hasMore` is false. Active drafts and customFields are included on the first page only (both fields are omitted once a `cursor` is supplied). Call read_message with a messageId from the timeline for attachments and full recipients.

read_conversation

Fetch a single message by ID with full content. Returns the message body (quoted replies stripped for clarity), recipients (from/to/cc/bcc), attachments, author, draft status, and delivery error type if applicable.

read_message

Check for additional tools whenever your task might benefit from a capability the available tools do not offer, even if an existing tool could work as a fallback. Front reviews these reports to add or clarify tools. Performs no action and changes nothing in Front; returns an acknowledgment and the names of the tools that exist.

request_tool

Search accounts (companies) by name.

search_accounts

Search contacts by name or email.

search_contacts

Search conversations by query and/or filters. Use the `filters` object to narrow by inbox, assignee, team, tags, status, or an absolute date range (after/before). `query` is optional when at least one filter is provided, so filters alone can list an inbox or a teammate's conversations.

search_conversations

Search the message templates (saved replies) the user can access: their personal templates and those of every workspace they belong to, the same set they see in the Front composer. Use this when the user refers to message templates or saved replies, or asks to reply using a standard or pre-written response. Templates are reply text, not a knowledge base: don't use this tool to answer questions about policies, products, or how to handle an issue. When the user has 50 templates or fewer, every template is returned, each page sorted by name, and query is not applied (query_applied: false), so judge which ones fit from their names and openings. With more than 50, query narrows to templates whose name, subject, or opening contain every query word, ranked by relevance, so use the words a template would contain, not a description of the situation; without a query, every template is returned, each page sorted by name. When fewer rows come back than total_count, page with offset before concluding a template is missing. If two differently worded queries don't surface a fitting template, tell the user none was found rather than searching further. Rows show each template's opening, not its body. To draft from a template, pass its id to create_draft as messageTemplateId; call again with message_template_ids only to show the user a full HTML subject and body, where variables such as {{recipient.first_name}} appear as unfilled placeholders.

search_message_templates

Send a draft message created via create_draft (queues it for delivery). Works for both reply drafts and new conversation drafts.

send_message

Add or remove tags on a conversation.

tag_conversation

Update a conversation's status. Provide exactly one of `status`, `statusId`, or `snoozeUntil`. Use `status` ("archived" / "open") to archive or reopen from the requester's point of view, matching the Front "Archive" / "Move to inbox" buttons: if the requester is the conversation's assignee (or it lives in their private inbox), the change is global — everyone with access sees the new status; if the requester is not the assignee on a shared conversation, only their personal view changes. Setting `status: "open"` on a snoozed conversation cancels its reminder. Use `statusId` (a ticket-status, sts_xxx, from list_statuses) to set the ticket status on a ticketing-enabled inbox — this also updates the conversation's open/archived state to match the status category. Setting a ticket status requires ticketing to be enabled. Use `snoozeUntil` (ISO-8601) to snooze the conversation until a given time; all snoozes also auto-cancel when an inbound message arrives.

update_conversation_status

Update the body, subject, or recipients of an existing draft. Pass the version from read_message for conflict detection — the call fails if the draft changed since you read it. Omitted fields are left unchanged; providing to/cc/bcc replaces that recipient list. Use takeOver:true to claim a draft you do not own.

update_draft

Update a task. Set `subject`, `description`, `dueAt`, `customFields`, or `accountIds` to change its values; `description` and `dueAt` take null to clear. Use `status` ("resolved" / "open") to resolve or reopen it, and `statusId` (a ticket status, sts_xxx, from list_statuses) to set its ticket status. Use `snoozeUntil` (ISO-8601) to archive it now and reopen it then. Every task state change goes through this tool rather than update_conversation_status. A task ID is a conversation ID.

update_task