Skip to main content
Glama

Video File Transcription

video_file_transcription

Converts video files into text transcripts using Whisper models, with optional timestamps, speaker labels, and language selection. Accepts URLs, data URIs, or base64 input and polls until done.

Instructions

Transcribe video file to text using Whisper models.

Extracts audio from video and converts it to text transcription with optional timestamps. Accepts video files as URLs (preferred), data URIs, or base64 strings. 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": "<video>",
      "include_ts": "<include_ts>"
    },
    "name": "video_file_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
videoYesVideo file as URL (preferred), data URI (data:video/mp4;base64,...), or base64 string. URLs are recommended to avoid base64 context bloat.
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
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
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

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: audio extraction, accepted input encodings, and automatic polling until the job finishes. It omits other relevant traits such as cost/credit implications (there is a dedicated price sibling), timeouts, and failure behavior on long jobs.

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, front-loaded with the core action, then accepted inputs, then async behavior. Minor redundancy between 'Transcribe video file to text' and 'converts it to text transcription'.

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 9-parameter tool with full schema documentation and an output schema, the description covers the essentials an agent needs: input encodings, extraction behavior, and polling. The main gap is routing guidance against the URL-based sibling, which is a usage concern rather than missing mechanics.

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 schema already explains lang, model, diarize, ts_level, webhook, and return_result_in_response in detail. The description only restates input formats and 'optional timestamps', adding little 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 ('Transcribe video file to text using Whisper models') and clarifies that audio is extracted then converted. It does not, however, explicitly differentiate itself from the sibling video_url_transcription, and by saying URLs are 'preferred' it actually blurs that boundary.

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: URLs are preferred over base64/data URIs to avoid context bloat, and the tool auto-polls until completion. There is no explicit statement of when to choose this over video_url_transcription or the corresponding audio tools, and no when-not guidance.

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