Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List LinkedIn profile comments

linkedin_live_person_comments_v2
Read-onlyIdempotent

Retrieve comments authored by a specific LinkedIn person using the required entity ID, with cursor support for paginated results.

Instructions

List comments authored by a LinkedIn person. Requires entityId. 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": {
      "entityId": "<entityId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "linkedin_live_person_comments_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
startNo
cursorNo
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
entityIdYesRequired. LinkedIn person entity ID. Not a vanity handle.
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.
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 the pagination mechanics (cursor) and the mandatory-identifier constraint, but says nothing about rate limits, ordering, or what a comment record 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 short sentences, front-loaded with the action and the required input, then the return shape and pagination hint. "Requires entityId" slightly duplicates the schema's required list, but the emphasis is defensible.

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?

There is no output schema, so the description carries the burden of describing the return value, yet it only says "Returns a list" with no indication of the comment fields returned. Also silent on empty-result and cursor-exhaustion behavior, which matters for a paginated list tool.

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% and the schema already documents entityId ("Not a vanity handle"), context, llm_model and conversation_id. The description reinforces that entityId is required and explains cursor as the pagination token, which is useful but marginal; it says nothing about `start`, `conversation_id`, or batching behavior.

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?

Specific verb + resource: "List comments authored by a LinkedIn person." This distinguishes it from activity-comment tools by scope (person-authored vs. activity-scoped), though it never names the sibling it is not, so an agent must infer the boundary from tool names 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?

States the hard prerequisite ("Requires entityId") and a pagination condition ("use cursor when paginated"), but gives no when-to-use vs. when-to-use-something-else guidance, e.g. versus linkedin_live_activity_comments_v2 or the person_posts 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