Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List LinkedIn profile posts

linkedin_live_person_posts_v2
Read-onlyIdempotent

Fetches posts from a LinkedIn person using their entity ID and returns paginated results with cursor support for reviewing their activity.

Instructions

List posts from 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_posts_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

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description does not need to restate safety. It adds useful behavioral context about requiring `entityId` and using `cursor` for pagination, though it does not discuss ordering, limits, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core action and prerequisite. There is no redundant or filler wording.

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?

For a simple read-only list tool with annotations and partial schema descriptions, the definition covers the essential entity requirement and pagination behavior. It could be stronger if it clarified `start` versus `cursor`, but it is broadly sufficient.

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 67%, and the description reiterates only `entityId` and `cursor` semantics. It does not add meaning beyond the schema for `context`, `llm_model`, `conversation_id`, or `start`.

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 posts from a LinkedIn person." The person scope helps distinguish it from organization-post tools, but the description does not explicitly contrast it with sibling profile or activity tools.

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?

Gives the key prerequisite that `entityId` is required and notes to use `cursor` when paginated. However, it does not explicitly say when to choose this tool over alternatives such as organization posts or search tools.

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