Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn post or article

linkedin_post_get
Read-onlyIdempotent

Retrieve the content of a LinkedIn post or article from a public permalink URL for analysis or reference.

Instructions

Get a LinkedIn post or article by URL. Requires url.

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_post_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Public permalink to the post or article.
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

C2.9/5.0
Behavior2/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 fully covered structurally. The description adds nothing further — no indication of what is returned (post text, article body, metadata), what happens with private or deleted posts, or any rate/usage constraints for an open-world fetch.

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?

Two short sentences, front-loaded with the verb and resource. The second sentence largely duplicates the schema's 'Required.' on `url`, making it slightly redundant but not harmful.

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?

For a simple read-only fetch with rich annotations and full schema coverage, the essentials for invocation are present. However, with no output schema, the description gives no sense of what a successful result contains, which is the main gap for an agent deciding between this and related fetch tools.

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 100%, including detailed notes for context, llm_model, and conversation_id, so the schema does the heavy lifting. The description only echoes the `url` requirement and adds no formatting or interpretation beyond what the schema already provides; baseline 3 applies.

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 ('Get a LinkedIn post or article by URL'), which is enough for an agent to identify the operation. It does not differentiate from the closely related sibling linkedin_post_transcript_get, leaving overlap between fetching a post and fetching its transcript unresolved.

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 a restatement of the required parameter ('Requires `url`'). There is no statement of when to choose this over linkedin_post_transcript_get or other article-get siblings, and no prerequisites such as the URL needing to be a public permalink (that detail lives only in the schema).

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