Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn post transcript

linkedin_post_transcript_get
Read-onlyIdempotent

Retrieve a LinkedIn post video transcript by URL to analyze or quote spoken content without manual transcription.

Instructions

Get the transcript for a LinkedIn post video 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_transcript_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the LinkedIn post whose video transcript should be returned.
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

B3.2/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 covered. Beyond that the description adds nothing — no indication of failure modes (post without video, private post), no note on transcript length/format, and no mention of the openWorld external-fetch implications. The only added statement, 'Requires `url`', merely restates the schema's required field.

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 action and resource, with no filler. The trailing 'Requires `url`' is redundant with the schema's required array and could be dropped, but the overall size is appropriate.

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 tool with full schema coverage, complete annotations, and no output schema, the definition is minimally sufficient. It is missing the one behavior an agent would want to know — what is returned or what error occurs when the LinkedIn post has no video — so it is adequate but not thorough.

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%, so all four parameters — including the unusual context, llm_model, and conversation_id fields — are already documented in the schema. The description only reiterates the url requirement and adds no syntax or format detail beyond it; baseline 3 applies when the schema does the work.

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 — 'get the transcript for a LinkedIn post video by URL' — which cleanly separates it from sibling lookups such as linkedin_post_get (the post itself) and from other platforms' transcript tools. It does not explicitly name an alternative, so it stops just short of full sibling differentiation.

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?

Usage is only implied by the noun phrase 'video transcript' — an agent can infer it applies when a transcript of a LinkedIn video is wanted. There is no explicit when-to-use/when-not, no guidance on choosing between this and linkedin_post_get, and no mention of what happens for posts without video.

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