LinkedIn MCP Server

Overview Schema Source Related Servers Discussions Admin

create_comment

Create a comment on a LinkedIn post or other entity by specifying the endpoint path and JSON body. Preview the comment by default, then execute to publish.

Instructions

Create comment at provided endpoint path. Preview by default.

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": {
      "path": "<path>",
      "body_json": "<body_json>"
    },
    "name": "create_comment"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`execute`	No
`body_json`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations present, the description carries the full disclosure burden and does reveal one consequential trait: 'Preview by default,' signaling that the default call does not mutate. However, it never explains what a preview returns, what execute=true does exactly, what side effects a real creation has, or whether authentication/scoping applies.

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 sentences that front-load the action and immediately follow with the key behavioral qualifier. Every word contributes; nothing is redundant or padded.

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 a tool with three parameters, zero schema descriptions, and no annotations, the description answers 'what' but not the practical 'how': valid path values, body_json structure, and execute=true behavior are all omitted. An output schema exists, but it does not compensate for the missing parameter semantics.

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 the description must compensate. It loosely maps path ('endpoint path') and execute ('Preview by default') but says nothing about body_json — its format, required fields, or content — leaving a required parameter completely undocumented.

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?

Uses a specific verb-resource pair ('Create comment') that distinguishes it from sibling tools like list_comments and create_post. The modifier 'at provided endpoint path' signals a path-driven creation model but does not obscure the core function. Clear enough for an agent to know what the tool does at a glance.

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

Usage Guidelines2/5

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

No guidance is given about when to choose this tool over alternatives such as create_post, create_reaction, or list_comments, and no prerequisites (auth state, existing post/comment) are mentioned. 'Preview by default' hints at invocation behavior but does not constitute usage guidance for tool selection.

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