Skip to main content
Glama
Sign In

LinkMCP: hosted LinkedIn MCP server

by io.linkmcp
OverviewDiscussionsAdmin

React to Post

linkedin_react_to_post
Destructive

React to a LinkedIn post or to a comment on it (like, celebrate, support, love, insightful, funny), as yourself or as a company page that you administer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "linkedin_react_to_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_pageNoOptional. React as a LinkedIn company page that you administer: the page_id from linkedin_list_company_pages. Omit it to react as yourself.
post_idNoActivity URN (urn:li:activity:123) or numeric activity ID. Use post_url or post_id, at least one is required.
post_urlNoLinkedIn post URL (e.g. https://www.linkedin.com/feed/update/urn:li:activity:123 or /posts/ style).
comment_idNoOptional. React to a specific comment instead of the post itself.
reaction_typeNoReaction type (default: "like").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / as_page
      Added value: +{
+  "description": "Optional. React as a LinkedIn company page that you administer: the page_id from linkedin_list_company_pages. Omit it to react as yourself.",
+  "type": "string"
+}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is carried structurally. The description adds the acting-identity distinction (yourself vs a page you administer), which is real context, but says nothing about whether an existing reaction is replaced or how to undo one — a meaningful gap given idempotentHint=false and destructiveHint=true.

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

Conciseness4/5

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

A single front-loaded sentence that leads with the verb and resource; nothing is padded. The parenthetical reaction list duplicates the schema enum and is the one element that does not earn its place.

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

Completeness3/5

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

With 0 required parameters, full schema coverage and annotations supplying the safety profile, the description covers the essentials for a small write tool. It still omits the 'at least one of post_id or post_url is required' constraint and the replace-vs-add behavior of an existing reaction, which are the main things an agent could get wrong.

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 every parameter is documented in the schema, including the post_id/post_url alternative and the as_page flow. The description only restates the reaction enum and the self/page option, adding no semantics the schema does not already carry, so the baseline of 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?

The description states a specific verb (React) and resource (a LinkedIn post or a comment on it), and enumerates the reaction types, so the operation is unmistakable. It implicitly differentiates from siblings like linkedin_comment_on_post and the read-only linkedin_get_post_reactions, but never names them or states the contrast explicitly.

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?

There is no when-to-use guidance, no statement of when to prefer this over linkedin_comment_on_post, and no prerequisites called out. The only routing hint (that as_page requires a page_id from linkedin_list_company_pages) lives in the schema, not the description.

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

All LinkMCP: hosted LinkedIn MCP server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources