LinkedIn MCP

linkedin_publish_approved_post

Publish a LinkedIn post through the official Posts API only after the caller explicitly confirms approval, ensuring posts are not shared without verified consent.

Instructions

Publish a post through LinkedIn's official Posts API only when the caller explicitly confirms approval.

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>",
      "approved": "<approved>"
    },
    "name": "linkedin_publish_approved_post"
  }
}

Input Schema

Name	Required	Default
`text`	Yes
`approved`	Yes
`visibility`	No	PUBLIC

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

B3.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add the useful behavioral gate (approval required) and identifies the underlying API, but omits that publishing is externally visible and effectively irreversible, whether it fails on duplicate content, and any rate limits.

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

Conciseness4/5

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

A single front-loaded sentence with no filler, and the approval condition lands before any caveat. It is lean to the point of under-specification for a mutation tool, but nothing in it is wasted.

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

Completeness2/5

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

For an irreversible external mutation with no annotations and no schema descriptions, the description leaves out visibility defaults, text constraints, failure/return behavior, and the relationship to the draft tool. The output schema covers return values, but the calling contract is still thin.

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 description coverage is 0%, so all three parameters are bare. The description explains the intent behind 'approved' but says nothing about 'text' (length/media constraints) or 'visibility' (its PUBLIC default and allowed values).

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

Purpose4/5

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

Names a specific verb ('publish a post') and the exact channel ('LinkedIn's official Posts API'), so the agent knows this is the live-publishing action rather than the drafting one. It stops short of naming the sibling it pairs with (linkedin_prepare_post), so differentiation is implied rather than explicit.

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

Usage Guidelines3/5

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

The precondition 'only when the caller explicitly confirms approval' gives an implied when-to-use rule, but the description never names linkedin_prepare_post as the drafting alternative nor says what to do when approval is not yet given. The caller must infer the two-step draft/publish workflow from the sibling list alone.

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

Deploy Server