linkedin-mcp

create_post

Publish a text post to LinkedIn with optional link attachment. Share updates or articles with your network.

Instructions

Publish a text post on LinkedIn as the authenticated member. Optionally attach a link (article share). For images use create_image_post.

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

Input Schema

Name	Required	Description
`text`	Yes	The post body (commentary).
`link`	No	Optional link to render as an article card.
`visibility`	No	Default PUBLIC.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Jun 22, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'publish' without detailing side effects, rate limits, idempotency, or permission requirements beyond being authenticated. The behavioral information is minimal.

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 sentences front-loading purpose and providing an alternative. Every sentence adds value with no fluff.

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 3-parameter tool with a nested object, the description covers usage and alternative but omits return value or error conditions. With no output schema, additional context would help, but it is minimally adequate.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description adds the phrase 'Optionally attach a link (article share)' which is helpful but largely redundant with the schema's description of the link parameter.

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 'Publish a text post on LinkedIn as the authenticated member', specifying the verb (publish), resource (text post), and platform. It also distinguishes from create_image_post for image sharing.

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 tells when to use this tool (text posts with optional link) and explicitly directs image posts to create_image_post. However, it does not address other sibling tools like reshare_post or comment_on_post, leaving some ambiguity.

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

Deploy Server