Reach MCP — LinkedIn for AI agents

like_post

Idempotent

Like a LinkedIn post on behalf of the connected account. Pass the post URL, slug, or URN. Use for a light touch on a post; idempotent on LinkedIn's side. Counts against the daily reactions quota.

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": {
      "account_id": "<account_id>",
      "post_url_or_urn": "<post_url_or_urn>"
    },
    "name": "like_post"
  }
}

Input Schema

Name	Required	Description
`page_id`	No	Act as this company page instead of the member: page_id (or vanity name) from list_managed_pages. The account must be an admin of the page with a role that allows the action. Omit to act as the member.
`account_id`	Yes	Reach id of the LinkedIn account to act on, from list_accounts.
`idempotency_key`	No	Optional. A key you choose (a UUID is fine) that names this exact call. If you retry with the same key and the same arguments, the first call's result is returned and nothing is done twice on LinkedIn. Reusing a key with different arguments is refused. Keys expire after 24 hours.
`post_url_or_urn`	Yes	LinkedIn post URL, slug, or urn:li:activity:…; a comment URN (urn:li:comment:(…)) likes that comment.

Output Schema

Name	Required	Description	Default
`liked`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / page_id

Added value: +{
+  "description": "Act as this company page instead of the member: page_id (or vanity name) from list_managed_pages. The account must be an admin of the page with a role that allows the action. Omit to act as the member.",
+  "type": "string"
+}

changedInput schema / properties / post_url_or_urn / description

Previous value: -"LinkedIn post URL, slug, or urn:li:activity:…."New value: +"LinkedIn post URL, slug, or urn:li:activity:…; a comment URN (urn:li:comment:(…)) likes that comment."

First observedSep 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Goes meaningfully beyond the annotations by disclosing that likes consume the daily reactions quota and that idempotency is enforced on LinkedIn's side, which is distinct from the local idempotency_key mechanism in the schema. It stops short of saying whether a like can be undone or what happens when the quota is exhausted.

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?

Four short sentences, action and identity front-loaded, with the quota warning placed at the end where it reads as a caveat. Minor redundancy: 'idempotent on LinkedIn's side' partially overlaps the idempotency_key parameter documentation.

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, and the actor, target, idempotency, and quota dimensions are all addressed. The remaining gap is failure behavior — what a quota-exceeded or permission-denied response looks like — but nothing essential to invoking it correctly is missing.

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%, so all four parameters, including the page_id admin-role nuance and idempotency_key expiry, are already documented there. The description's 'Pass the post URL, slug, or URN' largely restates the schema rather than adding new meaning, so it lands at the baseline.

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?

States a specific verb and resource ('Like a LinkedIn post') plus the acting identity ('on behalf of the connected account'), which cleanly separates it from siblings like comment_post, create_post, and react_message. An agent can pick it without opening the schema.

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?

'Use for a light touch on a post' gives an intent cue but is vague and never names alternatives (e.g. comment_post for substantive engagement) or states when not to like. The quota mention hints at a constraint but supplies no threshold or fallback, so usage is only implied.

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

All Reach MCP — LinkedIn for AI agents tools Inspect

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

Need Help?