Skip to main content
Glama

LinkedIn: react to post

linkedin_create_reaction
Idempotent

React to a LinkedIn post (like, praise, etc.). Publora has separate daily budgets for comment and reaction attempts, resetting at 00:00 UTC. Defaults are 5 each for Free/Starter and 20 each for paid Personal on the legacy app. Paid Personal on the Standard app can be exempt from the daily cap. Eligible business flows are exempt. Provider quotas and burst limits apply. Metered attempts share usage across channels, API, MCP and scheduled first comments. Sent attempts count even on failure. Use the backend response as the source of truth. If it returns LINKEDIN_DAILY_LIMIT_REACHED, wait until retryAt.

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": {
      "postedId": "<postedId>",
      "platformId": "<platformId>",
      "reactionType": "<reactionType>"
    },
    "name": "linkedin_create_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
postedIdYesLinkedIn post URN: urn:li:activity:<id>, urn:li:share:<id> or urn:li:ugcPost:<id>. From a LinkedIn post URL, preserve its exact activity ID as urn:li:activity:<id>; URLs are not accepted in this field. Never guess a share/ugcPost ID by replacing the activity prefix. Publora handles supported target translations.
platformIdYesPlatform connection ID
reactionTypeYesReaction type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds substantive behavior: attempts are metered, sent attempts count even on failure, quotas are shared across channels/API/MCP/scheduled comments, and the backend response is authoritative with retryAt on limit errors. The plan-by-plan budget detail is more than an agent needs, keeping it from a 5.

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

Conciseness3/5

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

Purpose is correctly front-loaded in the first clause, but the body spends several sentences on plan tiers and exemptions (Free/Starter vs legacy Personal vs Standard app vs eligible business flows) that an agent cannot act on. The actionable parts — metering, failure counting, retryAt — are buried mid-paragraph.

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?

For a three-parameter write action with no output schema, the description covers the important operational risks: idempotency expectations, quota consumption on failure, and explicit error recovery. Return-shape detail is unnecessary since it defers to the backend response as source of truth.

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 100% and the postedId field already documents URN formats and the no-URL/no-guessing rules, while reactionType carries an enum. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

"React to a LinkedIn post (like, praise, etc.)" gives a specific verb plus resource, and the parenthetical maps to the reactionType values. It is clearly distinguishable from linkedin_delete_reaction and linkedin_create_comment by name, though the description never explicitly contrasts them.

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 description tells the agent what to do on the LINKEDIN_DAILY_LIMIT_REACHED error (wait until retryAt), which is real operational guidance. However, it never says when to pick this over siblings such as linkedin_create_reshare or linkedin_create_comment, nor how to choose among the six reaction types.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.