Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Facebook post transcript

facebook_post_transcript_get
Read-onlyIdempotent

Retrieves the transcript of a Facebook post or Reel from its URL, so you can read or analyze spoken video content without watching.

Instructions

Get the transcript for a Facebook post or Reel 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": "facebook_post_transcript_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the Facebook post or reel whose 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.
allowLongTranscriptionNoLifts the 2-minute limit on AI transcription. A transcript then costs 10 credits per started minute of video, short clips included (plus the base 1), billed up to 60 minutes; a video with no transcript stays at the base price. Long videos can take a minute or more.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/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. The description adds nothing beyond that — it does not mention the AI-transcription nature, the default 2-minute limit, the credit cost of lifting it, or that long videos may take a minute or more (all of which live only in the schema).

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?

Two short sentences with zero waste, front-loading the action and the required input. Nothing is padded or repeated.

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?

There is no output schema, and the description says nothing about the shape of the returned transcript or the failure mode when a post has no transcript. The cost/latency trade-off for long transcription is left entirely to a single parameter's schema text, so the definition is adequate but not complete for a tool with real billing implications.

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 url, context, llm_model, conversation_id and allowLongTranscription are all documented in the schema itself. The description merely restates that url is required, adding no meaning beyond the structured data; 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 (Get) and resource (transcript for a Facebook post or Reel), plus the identifying input (by URL). An agent can distinguish it from facebook_post_get (post content) and from the platform-specific transcript siblings. It stops short of explicitly naming a sibling it is not.

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: you call it when you have a Facebook post/Reel URL and want the spoken content. There is no explicit when-to-use versus facebook_post_get, no note about what to do when no transcript exists, and no exclusion guidance.

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