Skip to main content
Glama

Video Url Transcription

video_url_transcription

Transcribe video from a URL into text using Whisper models, with optional timestamps and speaker labels. Supports YouTube, X, Twitch, Kick, and TikTok links.

Instructions

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.

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 observedv0.6.3

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does disclose one meaningful trait: it 'Automatically polls until transcription is complete', i.e. it blocks rather than returning a job id. It omits failure behavior, cost implications, and what is extracted, leaving the schema to carry the rest.

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?

Four short sentences, purpose first, then mechanism, then platform coverage, then the polling behavior. No filler, though the platform list duplicates the video_url schema description.

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?

An output schema exists, so return values need not be explained, and the schema is rich enough to cover all 10 parameters. Still, for a no-annotation, possibly costly, blocking transcription tool, the description says nothing about failure modes, latency, or cost, which an agent weighing this against the *_price sibling would want.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 description adds some meaning by naming supported URL forms and framing timestamps as optional, plus the Spaces routing note. It does not add detail on the lang/model/diarize/cost interactions, which the schema already covers.

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 ('Transcribe video from URL to text using Whisper models') and enumerates the supported platforms. It does not explicitly distinguish itself from the sibling variants (video_file_transcription, audio_url_transcription), so differentiation is only implied by the 'from URL'/'video' wording.

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?

No explicit when-to-use or when-not-to-use guidance relative to siblings such as video_file_transcription, audio_url_transcription, or the *_price tools. The only conditional routing mentioned ('A Twitter Spaces link is routed to audio transcription automatically') lives in the schema description, not the top-level description, so an agent gets no selection guidance here.

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