LinkedIn MCP Server

by oliverhruby

Overview Schema Source Related Servers Discussions Admin

Python

Local

create_post

Create a text post on LinkedIn with preview before publishing. Set execute=true to send the post directly to LinkedIn.

Instructions

Create a simple text post. Preview by default; set execute=true to send.

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": {
      "author_urn": "<author_urn>",
      "commentary": "<commentary>"
    },
    "name": "create_post"
  }
}

Input Schema

Name	Required	Default
`execute`	No
`author_urn`	Yes
`commentary`	Yes
`visibility`	No	PUBLIC
`distribution_feed`	No	MAIN_FEED

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It clearly discloses that the default action is a preview rather than an actual send, and that execute=true triggers the send. This is a key safety-relevant behavior. It does not discuss output shape or irreversible side effects, but the preview/execute split is meaningfully transparent.

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

Conciseness5/5

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

Two short, front-loaded sentences with no filler. The core purpose appears first, and the critical execution behavior appears immediately after.

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?

The description combined with the schema is enough to call the tool correctly: required params are visible, defaults are provided, and the preview/execute mechanism is stated. However, it omits what the preview response contains and does not explain the practical impact of visibility and distribution_feed defaults, with no annotations or output schema to fill those gaps.

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?

The description adds meaning only to the execute parameter ('set execute=true to send'). The required parameters author_urn and commentary, plus visibility and distribution_feed, receive no explanatory coverage. Since schema description coverage is 0%, the description must compensate more and does not.

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 states a specific verb and resource: 'Create a simple text post.' This clearly differentiates the tool from siblings like create_comment, create_reaction, and the media-upload tools in the sibling list.

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 a clear usage pattern: preview by default, and set execute=true to send. This tells the agent how to invoke the tool safely. It does not explicitly name alternative tools or exclusion conditions, but the resource is specific enough for basic selection.

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