SalesTouch Docs
All MCP tools
Writes to LinkedInLinkedIn

LinkedIn message

linkedin_message

Send a direct LinkedIn message to a member target.

When to use it

Send a direct message to an existing LinkedIn connection or known thread.

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

Requirements

Provide one member target: identifier, recipient, linkedin_url, profile_url, or handle.
Provide message content with text, message, or content.

Example

Ask your agent

Send “Thanks for connecting — happy to compare notes.” to https://www.linkedin.com/in/example.

Tool arguments
{
  "linkedin_url": "https://www.linkedin.com/in/example",
  "text": "Thanks for connecting — happy to compare notes.",
  "queue": true
}
MCP response envelope
{
  "content": [
    {
      "type": "text",
      "text": "{\n  \"data\": { ... },\n  \"meta\": null\n}"
    }
  ],
  "isError": false
}

Expected: A sent or queued message result with its action identifier.

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.

queue
boolean

Set true to queue this action when it cannot run now.

text
string

Message text to send.

message
string

Alias for text.

content
string

Alias for text.

thread_id
string

Optional existing LinkedIn thread id.

bypass_rate_limit
boolean

Bypass queued send limits when explicitly requested.

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.

action_limit_queue_required

Repeat the call with queue set to true.

message_requires_connection

Send an invitation or use invite_then_message instead.

On this page