Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List LinkedIn activity reactions

linkedin_live_activity_reactions_v2
Read-onlyIdempotent

Fetch reactions for a LinkedIn activity using its activity ID and page through results with a cursor.

Instructions

List reactions on a LinkedIn activity. Requires activityId. Returns a list (use cursor when paginated).

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": {
      "activityId": "<activityId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "linkedin_live_activity_reactions_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
startNo
cursorNo
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
activityIdYesLinkedIn activity ID.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the pagination mechanic, which is genuine value beyond the annotations, but it says nothing about rate limits, ordering, or what a page contains.

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?

Three compact sentences with the requirement front-loaded and no filler. It is appropriately sized for a simple list endpoint, though it leans on the schema for nearly all detail.

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 no output schema, the description should describe the returned shape; 'Returns a list' is thin. It also omits the conversation_id echo protocol that the schema treats as important for this tool's call sequence. Adequate for a simple reader, but not complete given the 6-parameter surface.

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 coverage is 67%, so the schema documents most parameters, including context, llm_model, and conversation_id. The description corroborates only `activityId` as required and gestures at `cursor`, adding no meaning for `start`, `conversation_id`, or the required `context`/`llm_model` analytics fields.

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 and resource ('List reactions on a LinkedIn activity'), which is enough to separate it from the sibling linkedin_live_activity_comments_v2 by resource subtype. It stops short of explicitly contrasting the two, but an agent can pick the right one from the wording alone.

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?

It supplies a hard prerequisite ('Requires `activityId`') and a procedural hint about cursors ('use cursor when paginated'), which implies the read/enumerate use case. There is no explicit when-to-use versus when-not guidance or named alternative for other activity sub-resources.

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