list_post_reactions — LinkedIn MCP tool reference

What it does

Everyone who reacted to a post — often a hundred named people interested in exactly one topic.

This tool drives a real LinkedIn account

It runs through a connected sender account in your workspace — not through a scraper and not through your own profile. Call list_sender_accounts first to see which identities are connected and healthy. If the workspace has none, this tool returns an error telling you so; accounts for agents covers how teams get one without risking their own profile.

Arguments

Name	Type	Required	Meaning
post	string	yes	Post URL, activity id, or URN (urn:li:activity:…, urn:li:ugcPost:…, urn:li:share:…)
comment_id	string	no	Reactions on this comment instead
limit	number	no	1–100 (default 50)
cursor	string	no	The `cursor` from the previous page, to continue
account	string	no	Sender account id or name to act as. Defaults to the healthiest connected account.

This table is generated from the literal inputSchema that tools/list returns, so what your client sees and what this page says are the same object:

inputSchema

{
  "type": "object",
  "properties": {
    "post": {
      "type": "string",
      "description": "Post URL, activity id, or URN (urn:li:activity:…, urn:li:ugcPost:…, urn:li:share:…)"
    },
    "comment_id": {
      "type": "string",
      "description": "Reactions on this comment instead"
    },
    "limit": {
      "type": "number",
      "description": "1–100 (default 50)"
    },
    "cursor": {
      "type": "string",
      "description": "The `cursor` from the previous page, to continue"
    },
    "account": {
      "type": "string",
      "description": "Sender account id or name to act as. Defaults to the healthiest connected account."
    }
  },
  "required": [
    "post"
  ]
}

Request

Paste this, swap the key, and you have called the tool.

curl

curl -s https://topclozer.com/api/mcp \
  -H "Authorization: Bearer tcz_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "list_post_reactions",
      "arguments": { "post": "urn:li:activity:7332661864792854528", "limit": 50 }
    }
  }'

Returns

{ post, count, cursor, reactions: [{ value, author: { providerId, name, headline, profileUrl, isCompany, networkDistance } }] }

The payload arrives inside an MCP content block — one text block whose body is this JSON, pretty-printed. Parse the string; there is no structured-content field.

payload

{ "post": "urn:li:activity:7332661864792854528", "count": 1, "cursor": null, "reactions": [{ "value": "LIKE", "author": { "providerId": "ACoAAC…", "name": "Priya N.", "headline": "SRE Lead", "isCompany": false, "networkDistance": "DISTANCE_3" } }] }

Rate limit

30 LinkedIn tool calls per 5 minutes, per workspace. Exceeding it returns HTTP 429 with JSON-RPC error -32002 and a Retry-After header. The budget is shared by every LinkedIn tool and counted per workspace, so minting a second key does not buy a second allowance.

The limit exists because an agent retrying in a loop is the request pattern that gets a LinkedIn account restricted, and a restricted account is a much worse outcome for you than a 429. Workspace tools do not spend this budget.

Related tools

list_post_comments

Comments on a LinkedIn post, or replies to one comment — with each commenter's headline and degree

check_reachability

Before reaching out: degree of connection, pending invitation, whether a connection request, a message or an InMail can go to this person — and whether the do-not-contact list or another account of the workspace already covers them

All 65 tools are listed on the tool index. Connecting a client is on the Claude setup page, and the protocol details are on the server page.