MCP tool reference · #191 of 563 by publishers
get_conversation
Exposed by 15 servers from 14 publishers, read from the live servers by the Serverdex check; most of them sit in Communication; 60% of them take a conversation_id parameter; the most-starred is Linked API (69 stars).
get_conversation(conversation_id: string, …)Parameters
share = % of the 15 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| conversation_id | string | 60% | 66.7% | From the send_message receipt (preferred). |
| id | string | 20% | 66.7% | Alias for conversation_id. Prefer conversation_id. |
| business_number | string | 13.3% | 0% | Scopes a `reference` to one business (references are reused across businesses). |
| reference | string | 13.3% | 0% | The 4-digit request reference, e.g. '4821'. Requires business_number. |
| after | string | 6.7% | 0% | The next_cursor of the previous page, to read the page after it. Omit for the first page. |
| conversationId | string | 6.7% | 100% | Conversation ID |
| kind | array | 6.7% | 0% | Activity view only: keep only these kinds of activity. Repeat for several. |
| limit | integer | 6.7% | 0% | How many records to return. Defaults to 25, maximum 100. |
| personUrl | string | 6.7% | 100% | The LinkedIn URL of the person whose conversation you want to poll (e.g., 'https://www.linkedin.com/in/john-doe') |
| room_name | string | 6.7% | 0% | Room name from list_conversations |
| since | string | 6.7% | 0% | Optional ISO 8601 timestamp to only retrieve messages since this date (e.g., '2024-01-15T10:30:00Z'). If not provided, the entire conversation history will be r |
| talent_slug | string | 6.7% | 0% | Talent slug (from search_talent results) — resolves to room name automatically |
Source: the input schema each server returns for get_conversation, aggregated over the 15 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with get_conversation
15 of 15 · 14 publishers · 15 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes get_conversation |
|---|---|---|---|---|---|---|
| 1 | Linked APIlinked-api · Communication | linked-api | Communication | 69 | yes | Legacy. Prefer get_inbox with personUrl. Retrieve a conversation with a LinkedIn person via standard LinkedIn messaging. Returns the conversation immediately if it has already been synced. If the conversation has not been synced yet, this tool starts a syncConversation workflow and returns its ack ({status, workflowId, operationName: "syncConversation", message}); the client should call get_workfl |
| 2 | Himalayas Remote Jobshimalayas-app · Business & CRM | himalayas-app | Business & CRM | 21 | yes | Get full message history for a conversation. Accepts room_name or talent_slug. Uses the connected Himalayas employer account; no extra sign-in needed. |
| 3 | EchoCallechocall-llc · AI & Agents | echocall-llc | AI & Agents | 1 | yes | Get a conversation Returns one conversation. The `type` query parameter selects which store the id is looked up in and must match the kind of record you are asking for, since voice calls and chat threads number themselves independently. A voice call is returned on its own. A chat conversation is returned together with its full transcript in `messages`, ordered oldest first and not paginated; for |
| 4 | CallMCP — Phone Call MCP Servercallmcp · Communication | callmcp | Communication | 1 | yes | Get a single SMS conversation thread by ID. |
| 5 | Stunt Doublestunt-double · AI & Agents | stunt-double | AI & Agents | 1 | yes | Get an actor conversation with its full message history, oldest message first. Find conversation ids with list_conversations. |
| 6 | KaiCallskaicalls · Communication | kaicalls | Communication | 1 | yes | Get a single SMS conversation thread by ID. |
| 7 | Weavdubdubdubco · Communication | dubdubdubco | Communication | — | yes | Get a Weav conversation, including recent messages. Pass conversation_id from search_conversations (that tool returns id). Do not use a customer, message, or other model id. |
| 8 | Cosendcosendhq · Communication | cosendhq | Communication | — | yes | Reads one conversation, named by id. view conversation returns the chat itself: its contact and newest message, its state, who it is assigned to, its labels, priority and snooze, the hand-over summary when a person is needed, who holds the reply lock, and the 24-hour customer service window (open or closed, and when it closes). view activity returns the chat’s activity feed one page at a time: han |
| 9 | Pipefiremikelovatt · Security & Identity | mikelovatt | Security & Identity | — | yes | The full email thread with one prospect: what was sent, what they replied, and the draft answer if one is waiting. Sending the answer is done in the Pipefire console (link included), never from here. |
| 10 | Clearlistcuneiform-llc · E-commerce & Retail | cuneiform-llc | E-commerce & Retail | — | yes | Read the full message history of a conversation thread with a buyer. Returns all messages (sender_type, content, timestamp) plus conversation metadata and reservation context. Use get_reservations first to find the conversation_id, then call this before reply_to_buyer to read what the buyer said. Every message carries `contains_public_text`. Where it is true, a member of the public typed some or a |
| 11 | Outil.iooutil-io · Communication | outil-io | Communication | — | yes | Fil complet (threadId de list_conversations) : messages reçus et envoyés de tous les canaux, envois automatiques, fiche contact et canaux où répondre (reply.ok, reason, until pour la fenêtre de 24 h). |
| 12 | SendItshree-git · Content & Publishing | shree-git | Content & Publishing | — | yes | Get full conversation thread with all messages. |
| 13 | SMS and WhatsApp Messagingbasilalshukaili · Communication | basilalshukaili | Communication | — | yes | Read a two-way conversation thread you started: its state, every message exchanged, and how many replies the business has sent. [free, requires key] |
| 14 | Agent Brokerbasilalshukaili · Legal & Government | basilalshukaili | Legal & Government | — | yes | Read a two-way conversation thread you started: its state, every message exchanged, and how many replies the business has sent. [free, requires key] |
| 15 | AIOProductOS MCPaioproductos · Data & Analytics | aioproductos | Data & Analytics | — | yes | Read one support conversation: the visitor plus the full message thread, oldest first. Read-only. Resolve the conversation_id first with list_conversations — never guess it. |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.