Skip to main content
Glama

Video Url Transcription

video_url_transcription

Transcribe video from URL to text using Whisper models.

Extracts audio from video URL and converts it to text transcription with optional timestamps. Supports YouTube, Twitter/X, Twitch, Kick and TikTok videos. Automatically polls until transcription is complete.


Available models:

  • WhisperLargeV3Ct2: ts_level: segment|word, diarize, output=json (text + segments)

  • WhisperLargeV3: ts_level: segment

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": {
      "video_url": "<video_url>",
      "include_ts": "<include_ts>"
    },
    "name": "video_url_transcription"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the recording as an ISO code, e.g. 'en', 'pl'. Set it whenever you know the language: auto-detection can pick the wrong one, e.g. on short or accented audio. It forces the output language, so a wrong code returns a translation instead of a transcript. Auto-detected when unset
modelNoWhisper model from the model list. Default WhisperLargeV3Ct2: honours lang, returns segments, supports diarize and word timestampsWhisperLargeV3Ct2
diarizeNoLabel who is speaking; implies include_ts. Only on models marked 'diarize' in the model list (WhisperLargeV3 rejects it). Costs 1.5x, not stacked with a finer ts_level
ts_levelNoTimestamp granularity: 'segment', 'word' or 'char'; implies include_ts. Only the levels a model lists under 'ts_level' in the model list are accepted (WhisperLargeV3: segment only). Finer than segment costs 1.5x on models that price it
video_urlYesURL of video to transcribe. Supports YouTube (e.g., 'https://www.youtube.com/watch?v=...'), Twitter/X (e.g., 'https://twitter.com/user/status/...' or 'https://x.com/user/status/...'), Twitch (e.g., 'https://www.twitch.tv/videos/...'), Kick (e.g., 'https://kick.com/video/...') and TikTok. A Twitter Spaces link is routed to audio transcription automatically
include_tsYesInclude timestamps in transcription
webhook_urlNoHTTPS URL for deAPI to call when this job finishes. Notifies your own systems; the tool still returns the result here
webhook_secretNo32-255 char key deAPI signs the callback with (HMAC-SHA256). Needs webhook_url. A secret given in chat stays in the transcript
include_metadataNoInclude source metadata in the result. Carries a flat surcharge on models that price it
return_result_in_responseNoReturn transcription inline. Set to False for large files to get download URL instead

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose key behavior: it automatically polls until completion, and the model list explains which models support diarization and word timestamps. It does not cover auth, rate limits, or failure modes, but the polling and model-capability disclosure is substantive.

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?

Front-loaded with the core action and platform scope, then a clearly delimited model list. The model list is cut off mid-entry ('WhisperLargeV3: ts_level: segment'), which slightly undercuts completeness but the structure is otherwise efficient.

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?

An output schema exists, so return values needn't be explained, and all ten parameters are documented in the schema. The description covers platforms, polling, and model capabilities; only explicit sibling routing guidance is missing for a tool of this complexity.

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 coverage is 100%, so the schema already documents all ten parameters thoroughly, including cost multipliers and constraints. The description's model list adds some cross-parameter meaning (which model accepts diarize/ts_level), but the truncated final line limits the added value, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Transcribe video from URL to text using Whisper models') and enumerates the supported platforms (YouTube, Twitter/X, Twitch, Kick, TikTok). The name plus description make it distinguishable from the audio and file transcription siblings without opening a schema.

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 context is implied by the platform list and the note that Twitter Spaces links are routed to audio transcription, but there is no explicit when-to-use-this-vs-alternatives guidance (e.g., use video_file_transcription for local files, or the _price sibling to estimate cost). The agent must infer routing from names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.