Skip to main content
Requires the Inbox or Unibox permission. Tools in this group are hidden from tools/list and refused on call when your plan does not grant it.

conversation_get

Write One thread with its full message history, the lead behind it, and which campaign it came from. Note the side effect: reading a thread marks it seen, so do not call it to browse unless the user wants the badge cleared. This is the prospect-facing exchange. For what an AI agent reasoned on its way to a reply use agent_logs, and for the lead’s step history lead_get.

Parameters

string
required
Conversation id, from conversation_list.
boolean
default:"true"
Include the full message thread. Can be long.

conversation_list

Read-only The unified inbox: LinkedIn and email threads with prospects, newest activity first, 20 per page. This is where replies land. Filter by campaignId to review one campaign’s responses, or keyword to find a specific person. Threads, newest first — the conversation view. For one thread’s messages use conversation_get, for the person behind it lead_get, and for campaign reply counts rather than the threads themselves analytics_campaign. Nothing here sends: there is no tool to send an inbox message.

Parameters

string
Only threads on this LinkedIn account.
string
Only threads on this mailbox.
string
Campaign id, from campaign_list or campaign_create.
string
Search names and message bodies.
string
Comma-separated tag ids.
string
Thread kind, e.g. “email”.
string
Filter by channel, e.g. “linkedin” or “email”.
integer (min 1)
default:"1"
1-indexed page number.

conversation_mark_all_read

Write Clear the unread badge across every thread on one LinkedIn account. Blunt and account-wide — it marks everything read, including threads nobody has looked at, so confirm before using it to tidy a badge. For one thread use conversation_update.

Parameters

string
required
LinkedIn account id, from linkedin_account_list.

conversation_update

Write Archive a thread, mark it read, or hand it between the AI assistant and a human. Setting assistant: false stops the bot replying so a person can take over — the one call to make when an agent is answering badly and a human needs the thread. Scope is this thread: it does not stop the agent elsewhere (agent_upsert with isActive: false), detach it from the campaign (campaign_update), or change the lead itself (lead_update). It cannot send a reply either.

Parameters

string
required
Conversation id, from conversation_list.
boolean
Move out of the main list without deleting.
boolean
Mark as read.
boolean
Whether the AI agent handles this thread.
boolean
Automatically stand the bot down as soon as a human sends a message here.

message_draft_ai_reply

Write Ask a connected AI provider to draft a reply for a thread, given a prompt. Returns the draft only — give it to the user to send themselves, because sending an inbox message has no tool at all and no substitute. This is a one-off draft from a prompt. A configured agent that replies on its own is agent_upsert plus campaign_update; to see how such an agent would answer, agent_query. Requires an AI provider connected in the web app under Settings - Integrations.

Parameters

string
required
Conversation id, from conversation_list.
OPENAI | ANTHROPIC | GEMINI | GROK | DEEPSEEK
required
Which connected provider to use. Providers are connected in the web app.
string
required
What the reply should do, e.g. “propose three times next week for a 20-min call”.

saved_reply_list

Read-only Reusable reply snippets your team keeps for common inbox situations. Text a human can copy when replying by hand. These are not sequence steps (flow_get), not agent FAQs (agent_get), and nothing here is sent automatically. No parameters.

saved_reply_upsert

Write Destructive
Marked destructive in the protocol — your MCP client asks for confirmation before running it.
Create a saved reply, or update one by passing savedRepliesId. Stores a snippet for humans to reuse; it does not send anything, schedule anything, or teach an agent — agent wording lives in agent_upsert. There is no tool to delete a saved reply.

Parameters

string
Omit to create a new one.
string
required
Short label shown in the reply picker.
string
required
Body. Supports {{firstName}}-style merge fields.
string[]
Restrict visibility to these team member ids.