Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List LinkedIn company posts

linkedin_company_posts_list
Read-onlyIdempotent

List posts from a specific LinkedIn company page by URL to retrieve its published updates, with page-based pagination for additional results.

Instructions

List posts from one specific LinkedIn company page by URL (not a keyword search — use linkedin_posts_search_list to search across public posts). Requires url. Returns a list (use page 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": {
      "url": "<url>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "linkedin_company_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. LinkedIn company page URL or slug whose posts should be listed.
pageNo1-based results page number. Pagination is page-based; at most 7 pages can be requested for a given company.
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.
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

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the useful facts that a URL (not a keyword) is required and that results are a list that should be paginated via `page`. It stops short of describing ordering, limits per page, or edge cases such as invalid slugs.

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?

A single front-loaded sentence covers scope, the alternative tool, the required parameter, and the return shape with no wasted wording. Parentheticals are used precisely for the exclusion and the pagination hint.

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 read-only list tool with rich annotations and a fully described schema, only the return shape and pagination guidance need describing, and both are present. Minor gaps remain around result ordering and what an unrecognized URL yields, but no output schema exists to cover return semantics and the description does what is needed.

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 100%, so `url`, `page` (1-based, max 7), `context`, `llm_model` and `conversation_id` are all already documented. The description only restates that `url` is required and that `page` handles pagination, adding no syntax or format detail beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource (list posts from one specific LinkedIn company page by URL) and immediately scopes it away from the keyword-based sibling by naming `linkedin_posts_search_list`. An agent can distinguish it from the other `*_posts_list` tools without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit selection rule: use this for a single company page by URL, and use `linkedin_posts_search_list` when searching across public posts by keyword. The alternative is named and the condition that selects it is stated.

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