LinkedIn MCP Server

Overview Schema Source Related Servers Discussions Admin

Prepare LinkedIn Message

linkedin.messaging.message.prepare

Idempotent

Prepare a LinkedIn message draft with text, emoji, file attachments, and GIFs for an existing conversation or profile, optionally replying to a specific message. Does not send.

Instructions

Open one visible one-to-one standard conversation, using the exact profile's Message button for profile targets and accepting its recipient-bound compact pane or following its exact visible Messaging href in the same operation page, then create an immutable message draft containing exact text/emoji, hash-locked current desktop file attachments, one exact KLIPY GIF title, and optionally an exact reply-to message_ref. This does not send the message. Group chats, message requests, and paid InMail are excluded.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context_id": "<context_id>",
      "request_id": "<request_id>"
    },
    "name": "linkedin.messaging.message.prepare"
  }
}

Input Schema

Name	Required	Description	Default
`gif`	No
`message`	No
`context_id`	Yes
`request_id`	Yes
`attachments`	No
`profile_slug`	No
`conversation_id`	No
`conversation_ref`	No
`reply_to_message_ref`	No

Output Schema

Name	Required	Default
`draft`	Yes
`status`	No	ready_for_confirmation
`sources`	Yes
`replayed`	No
`context_id`	Yes
`request_id`	Yes
`approval_preview`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 14, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds meaningful behavioral detail beyond the annotations: it opens a visible conversation, uses the exact profile Message button or Messaging href, creates an immutable draft, hash-locks attachments, allows exactly one KLIPY GIF, and optionally a reply_to_message_ref. These complement the idempotentHint and destructiveHint=false without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description packs substantial detail into three sentences. The first sentence is a long, convoluted run-on that is hard to parse, though it is front-loaded with the core action. The following two sentences are clear and direct.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 9-parameter tool with zero schema descriptions, the description covers behavioral constraints and exclusions well, and an output schema exists so return values need not be explained. However, key parameters like context_id and request_id are left unexplained, and the interplay between profile_slug, conversation_id, and conversation_ref is ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage. The description references message, gif, attachments, and reply_to_message_ref conceptually but does not clearly explain the mandatory context_id, request_id, or the conversation/profile identifiers (profile_slug, conversation_id, conversation_ref). This leaves the agent to guess at crucial routing and correlation parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool opens a one-to-one conversation and creates an immutable draft, explicitly noting it does not send. It distinguishes itself from the sibling execute tool by saying 'This does not send the message' and lists excluded conversation types.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context: use this to prepare but not send a message, with explicit exclusions (group chats, message requests, paid InMail). It implies the companion execute tool for sending, though it doesn't name it directly or provide a formal when/when-not split.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server