Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List LinkedIn activity comments

linkedin_live_activity_comments_v2
Read-onlyIdempotent

List comments on a LinkedIn activity using the activity ID, and paginate results with a cursor to review large comment threads.

Instructions

List comments 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_comments_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
startNo
cursorNo
sortByNorelevance
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 readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds that results come back as a list with cursor-based pagination, but omits the schema-stated sequencing rule (no parallel calls until conversation_id is received) and any rate-limit or result-shape context.

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 short sentences, front-loaded with purpose followed by the hard requirement and pagination note. No waste, though the parenthetical phrasing is slightly terse.

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?

No output schema exists and the tool has 8 parameters including required analytics fields and a conversation_id sequencing contract, none of which the description addresses. Adequate to start a call but leaves meaningful behavioral requirements to the schema.

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 50% with 8 parameters; the description only clarifies that `activityId` is required and that `cursor` is used for pagination. It adds nothing about count, start, sortBy, or the mandatory context/llm_model analytics parameters, so it only partially compensates for the coverage gap.

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?

States a specific verb and resource ("List comments on a LinkedIn activity") and names the required identifier, which distinguishes it functionally from the sibling person-comments tool by resource type. It does not explicitly name the sibling it is not, so it falls short of a 5.

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?

Usage is only implied: the description says it requires `activityId` and hints at pagination, but it offers no when-to-use/when-not guidance and does not route the agent to the person-level comments tool or the activity get tool.

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