LinkedIn MCP Server

Overview Schema Source Related Servers Discussions Admin

Publish Prepared LinkedIn Comment

linkedin.posts.comment.execute

DestructiveIdempotent

Execute an approved LinkedIn post comment, submitting exactly one immutable personal top-level comment after verification and idempotency checks.

Instructions

Account-changing action. Invoke only when the MCP client's configured approval policy authorizes this exact execute tool. Interactive confirmation is the safe default; an explicit durable per-tool approval may authorize unattended execution. Submit exactly one immutable personal-member top-level comment after the server verifies the preview, actor, target author, payload, local asset hash, expiry, and idempotency.

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>",
      "action_id": "<action_id>",
      "payload_hash": "<payload_hash>",
      "approval_preview": "<approval_preview>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "linkedin.posts.comment.execute"
  }
}

Input Schema

Name	Required	Description
`action_id`	Yes	Immutable action ID returned by the matching prepare tool.
`context_id`	Yes
`request_id`	Yes
`payload_hash`	Yes	Exact payload hash returned by the matching prepare tool.
`idempotency_key`	Yes
`approval_preview`	Yes

Output Schema

Name	Required	Default
`result`	Yes
`status`	No	completed
`sources`	Yes
`replayed`	No
`context_id`	Yes
`request_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 14, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description discloses account-changing behavior beyond annotations, including 'immutable', 'exactly one', and the verification steps (preview, actor, target author, payload, local asset hash, expiry, idempotency). It also explains approval default vs. durable approval, providing actionable context not in the annotations.

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?

The description is three sentences, front-loaded with the critical 'Account-changing action' warning. Every sentence adds value—approval policy, verification, and immutability—without redundancy.

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

Completeness4/5

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

Given the output schema and annotations, the description covers the essential behavioral safeguards and execution constraints. It could explicitly point to the matching prepare tool, but the schema and sibling context provide that linkage, so it remains complete enough.

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 description coverage is only 33%, so the description must compensate. It mentions verification of 'payload, local asset hash, expiry, and idempotency' which maps to payload_hash and idempotency_key, but it does not explain context_id, request_id, or approval_preview individually. Partial compensation at best.

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 uses a specific verb and resource: 'Submit exactly one immutable personal-member top-level comment', which clearly states the tool's action and scope. It distinguishes itself from the sibling prepare tool by emphasizing execution and verification.

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?

It provides a clear when-to-use condition: 'Invoke only when the MCP client's configured approval policy authorizes this exact execute tool.' It also implies a prepare-then-execute workflow with 'after the server verifies the preview...', though it does not explicitly name alternatives or exclusions.

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

Deploy Server