Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List LinkedIn organization posts

linkedin_live_organization_posts_v2
Read-onlyIdempotent

Lists posts published by a LinkedIn organization using its numeric organization ID. Returns paginated results with a cursor so you can retrieve the full post history.

Instructions

List posts from a LinkedIn organization. Requires organizationId. 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": {
      "organizationId": "<organizationId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "linkedin_live_organization_posts_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.
organizationIdYesNumeric LinkedIn organization 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.2/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 without the description. The description adds the pagination behavior ('use cursor when paginated') and the required identifier, which is useful, but it omits how many posts are returned per page or what fields each post 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 purpose, then prerequisite, then return/pagination behavior. Nothing is wasted, though 'Requires `organizationId`' repeats the schema's required list.

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?

The tool is simple (a read-only paginated list) and annotations plus schema cover most of the burden. However, 'use cursor when paginated' is vague about where the cursor comes from in the response, and with no output schema the description could have said more about the returned list's shape.

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?

With 67% schema description coverage, most parameters are documented in the schema itself, including context, llm_model and conversation_id. The description only clarifies that organizationId is mandatory and that cursor drives pagination, adding little beyond the structured 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 uses a specific verb and resource: 'List posts from a LinkedIn organization,' which is unambiguous about what is returned. It does not name the sibling it differs from (e.g. linkedin_live_person_posts_v2 or linkedin_posts_search_list), so an agent must infer the org-vs-person distinction from the ID type alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is the prerequisite 'Requires `organizationId`,' which restates a required schema field. There is no statement of when to choose this over the many sibling post/search tools, and no exclusions or conditions given.

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