Skip to main content
Glama
Sign In
LinkedIn MCP Server

LinkedIn MCP Server

by prakharagarwal-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Apply Prepared LinkedIn Post Reaction

linkedin.posts.reaction.execute
DestructiveIdempotent

Execute approved LinkedIn post reaction actions: set, change, or remove reactions after verifying preview and authorization.

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. Set, change, remove, or safely no-op one prepared exact reaction state after the server verifies the preview, actor, target author, prior state, 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.reaction.execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
action_idYesImmutable action ID returned by the matching prepare tool.
context_idYes
request_idYes
payload_hashYesExact payload hash returned by the matching prepare tool.
idempotency_keyYes
approval_previewYes

Output Schema

NameRequiredDescriptionDefault
resultYes
statusNocompleted
sourcesYes
replayedNo
context_idYes
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Discloses the account-changing nature, the server-side verification checks (preview, actor, target author, prior state, expiry, idempotency), and the possibility of a safe no-op. This goes well beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=true) by detailing what the tool does and what safety mechanisms exist.

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?

Three dense sentences with no redundancy. The description front-loads the safety/approval warning and then delivers the core action in a compact, well-structured way.

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

Completeness5/5

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

For a high-stakes execute tool, the description covers approval requirements, behavioral scope, server verification, and idempotency, while the output schema handles return values. An agent has sufficient information to safely select and invoke the tool.

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%, and the description does not individually explain the six parameters. However, it does tie key execution concepts (preview, actor, idempotency, expiry) to the flow, adding modest semantic context beyond the schema. It does not fully compensate for the low coverage.

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's function: set, change, remove, or safely no-op a prepared LinkedIn post reaction after server verification. It distinguishes itself from the prepare sibling and other execute tools by emphasizing 'prepared exact reaction state' and the execute-only scope.

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?

Provides an explicit invocation rule: only call when the MCP client's approval policy authorizes this exact execute tool, with interactive confirmation as the safe default and durable approval for unattended runs. While it doesn't name alternate tools, it gives clear when/when-not context via the approval gate and the prepare/execute split implied by 'prepared.'

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

Deploy Server

Other Tools