Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Twitter tweet transcript

twitter_tweet_transcript_get
Read-onlyIdempotent

Retrieve a video tweet transcript by URL to read or analyze spoken content without watching the video.

Instructions

Get the transcript for a video tweet by URL. Requires url. Pass url (tweet permalink or numeric id), not tweetId/tweetUrl.

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": "twitter_tweet_transcript_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Tweet permalink or numeric id.
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered without the description's help. The description adds little behavioral context beyond the parameter naming caveat, and says nothing about what happens for a video with no available transcript (the schema notes that case only in the pricing context).

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, front-loaded with purpose then the parameter constraint. No filler or restated annotation boilerplate.

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, idempotent getter with a fully described five-parameter schema and no output schema, this description covers the essentials an agent needs to invoke it. The minor gap is error/empty-transcript behavior, which is only obliquely referenced in the schema's pricing note.

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 the baseline is 3; the schema already documents url, context, llm_model, conversation_id and allowLongTranscription in detail including pricing and limits. The description's only addition is the negative convention ('not tweetId/tweetUrl'), which is a small but genuine anti-pattern warning beyond the schema.

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 gives a specific verb and resource ('Get the transcript for a video tweet'), scoping it to video tweets rather than tweets generally, which separates it from twitter_tweet_get. It does not explicitly contrast itself with the parallel transcript tools for other platforms, but the platform qualifier makes the intent unambiguous.

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 resource name; there is no explicit statement of when to choose this over twitter_tweet_get or how to handle non-video tweets. The only actionable guidance is about which parameter name to supply, not when the tool is appropriate.

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