Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get TikTok video transcript

tiktok_video_transcript_get
Read-onlyIdempotent

Fetch the spoken transcript of a TikTok video using its URL. Convert video speech into readable text for quoting or analysis.

Instructions

Get the spoken transcript for a TikTok 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": "tiktok_video_transcript_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the TikTok video whose transcript should be returned.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
languageNoOptional two-letter language code to request a transcript in a specific language when available.
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.
useAiFallbackNoWhen true and the video has no caption track, transcribes the audio with AI (videos up to 2 minutes). Adds 10 credits only when AI produced the transcript (11 total); caption reads and empty results stay at 1 credit.
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.
allowLongTranscriptionNoRequires useAiFallback=true. Lifts the 2-minute AI limit. An AI transcript then costs 10 credits per started minute of video, short clips included (plus the base 1); caption reads and empty results stay at 1 credit. 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
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing about credit costs, latency, or fallback behavior — those appear only in the schema — but it does not contradict the annotations either.

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, zero filler, with the required input front-loaded immediately after the purpose. Nothing could be removed without losing information.

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 7-parameter tool with credit implications and a 2-minute AI limit, the description is thin — it never signals cost or latency risks that an agent might want before calling. However, the rich schema compensates for most of this, and no output schema exists to explain return values.

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 every parameter including useAiFallback, allowLongTranscription, language and credits economics is already documented in structured form. The description only restates that `url` is required, adding no meaning beyond the schema; 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 the spoken transcript') scoped to a platform ('TikTok video') and the input ('by URL'). An agent can distinguish it from tiktok_video_get or tiktok_video_download_get by the transcript focus, though it never names those alternatives explicitly.

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?

There is no when-to-use or when-not-to-use guidance, no mention of caption-vs-AI-fallback tradeoffs, and no pointer to sibling tools. All decision-relevant guidance lives in the schema, not the description.

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