Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search LinkedIn posts

linkedin_posts_search_list
Read-onlyIdempotent

Search public LinkedIn posts site-wide by keyword to find relevant discussions, with optional filters for recency such as last day, week, or month.

Instructions

Search public LinkedIn posts site-wide by keyword (not scoped to one profile or company — use linkedin_live_person_posts_v2 or linkedin_company_posts_list for that). Requires query. Returns a list (use cursor when paginated). datePosted takes last-hour, last-day, last-week, last-month or last-year.

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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "linkedin_posts_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Keyword or phrase to search for in public LinkedIn posts.
cursorNoOpaque pagination cursor returned by a previous response.
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.
datePostedNoOptional filter for how recently matching posts were published.
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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds return-shape information the annotations do not: results come back as a list and pagination is cursor-based. It says nothing about result caps, rate limits, or auth, so it stops short of a 5.

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?

Three tight sentences, front-loaded with scope and the sibling exclusions, followed by the required-parameter note and return/pagination note. Every clause carries information; the parenthetical exclusion is the most valuable part and comes early.

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 search with no output schema, telling the agent it returns a list and that pagination uses the cursor is the key missing piece and it is present. Gaps remain around result volume limits and whether the search covers full post bodies, which would matter for a site-wide search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds some meaning beyond the schema: it restates that `query` is required for selection, and it enumerates the accepted `datePosted` values in prose. The enumeration duplicates the schema enum, but the required-parameter emphasis helps an agent avoid a failed call.

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?

States a specific verb and resource ('Search public LinkedIn posts') plus an explicit scope ('site-wide', not scoped to one profile or company), and names the sibling tools that handle the scoped case. An agent can distinguish this from linkedin_company_posts_list without opening either 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 routing rule: use this for site-wide keyword search, use `linkedin_live_person_posts_v2` or `linkedin_company_posts_list` when the target is a single person or company. Also flags the required parameter up front, leaving nothing to inference about when this tool applies.

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