LinkedIn MCP Server

Overview Schema Source Related Servers Discussions Admin

Prepare LinkedIn Post Reaction

linkedin.posts.reaction.prepare

Idempotent

Inspect a LinkedIn post's current reaction and prepare a target reaction state (none, like, celebrate, support, love, insightful, or funny) without changing the post. Provides a safe immutable plan for reaction updates.

Instructions

Inspect the exact current reaction state on one visible post and prepare an immutable target state: none, like, celebrate, support, love, insightful, or funny. This tool never changes the reaction.

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>",
      "post_ref": "<post_ref>",
      "desired_reaction": "<desired_reaction>"
    },
    "name": "linkedin.posts.reaction.prepare"
  }
}

Input Schema

Name	Required	Description	Default
`post_ref`	Yes
`context_id`	Yes
`request_id`	Yes
`desired_reaction`	Yes

Output Schema

Name	Required	Default
`draft`	Yes
`status`	No	ready_for_confirmation
`sources`	Yes
`replayed`	No
`context_id`	Yes
`request_id`	Yes
`approval_preview`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations provide idempotentHint=true and readOnlyHint=false, which are broad. The description adds that the operation never changes the reaction and that the target state is immutable, which is more specific than annotations. Yet it does not disclose what other side effects preparation may entail (since readOnlyHint=false suggests some write), leaving a minor gap.

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 concise sentences, front-loaded with the core action and clear boundaries. Every word earns its place with no 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?

An output schema exists, so return values need no explanation. The description is adequate for basic selection and invocation, but it omits the relationship to the execute step, prerequisites of 'visible post', and did not explain all required parameters. Still, it is mostly complete for a prepare tool.

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?

With 0% schema description coverage, the description must explain the parameters. It covers desired_reaction by listing all valid values and post_ref as 'visible post', but context_id and request_id are not explained. Since these are required and likely serve idempotency/context purposes, the description fails to compensate for the missing schema details.

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 the tool inspects the current reaction state on a visible post and prepares an immutable target state, explicitly listing all allowed values. It also distinguishes itself from the execute sibling by stating 'This tool never changes the reaction.' This is a specific verb + resource with clear differentiation.

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 provides good context: it is for a single visible post, it captures the exact current state, and it prepares a target state. However, it does not explicitly mention when to use this instead of the execute tool or any alternative, though the statement 'never changes the reaction' implies it is a read-only/preparation step.

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

Deploy Server