SalesTouch Docs
All MCP tools
Read onlyLinkedIn

LinkedIn conversation messages

linkedin_conversations_messages

List messages from one LinkedIn conversation resolved from a chat id or profile target.

When to use it

Load the message history for a known conversation or member.

Required scopes
linkedin:accesssalestouch:use
Execution
Synchronous MCP tool call

Requirements

Provide a conversation_id/chat_id/thread_id or a member target.
account_id is optional when SalesTouch can resolve a connected account automatically.

Example

Ask your agent

Read my full LinkedIn message history with https://www.linkedin.com/in/example, oldest first.

Tool arguments
{
  "linkedin_url": "https://www.linkedin.com/in/example",
  "limit": 100,
  "order": "oldest_first"
}
MCP response envelope
{
  "content": [
    {
      "type": "text",
      "text": "{\n  \"data\": { ... },\n  \"meta\": null\n}"
    }
  ],
  "isError": false
}

Expected: Normalized messages plus conversation participants and pagination state.

Parameters

account_id
string

Connected LinkedIn account id, remote id, username, email, handle, or account URL.

identifier
string

LinkedIn member handle, provider id, public id, or profile URL.

recipient
string

Alias for identifier when sending to a member.

linkedin_url
string

LinkedIn profile URL.

profile_url
string

Alias for linkedin_url.

handle
string

LinkedIn public identifier or local handle.

cursor
string

Pagination cursor.

before
string

ISO 8601 UTC datetime upper bound.

after
string

ISO 8601 UTC datetime lower bound.

conversation_id
string

LinkedIn conversation id or provider chat id.

chat_id
string

Alias for conversation_id.

thread_id
string

Alias for conversation_id.

limit
number

Maximum messages to return. Defaults to 50, max 250.

sender_id
string

Filter messages by provider sender id.

include_participants
boolean

Include normalized conversation attendees. Defaults to true.

order
string

Message order: oldest_first or newest_first. Defaults to oldest_first.

Aliases are shown independently because MCP clients send a flat JSON object. Use one alias from each required group, not every alias.

Common errors

insufficient_scope

Reconnect the MCP and approve the requested LinkedIn permission.

paid_plan_required

Use a SalesTouch workspace with LinkedIn MCP access.

On this page

When to use itRequirementsExampleParametersCommon errorsRelated tools