Skip to main content
Glama

Video File Transcription

video_file_transcription

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.


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": "<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 observed

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; it does disclose a real behavioral trait, 'Automatically polls until transcription is complete,' and the model capability constraints. It omits whether the operation is billed, what happens on long jobs or timeouts, and any file-size limits, which matters because sibling *_price tools signal that cost is a first-class concern.

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?

Purpose and input formats are front-loaded in two sentences before the model list, and nothing is padded. The model section is slightly redundant with the schema and is cut off mid-entry, which is the only structural weakness.

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, the schema is fully described and an output schema exists, so return values need no explanation. The description adds the key non-schema facts (auto-polling, preferred input form, model capability gating), though it never mentions cost or failure handling for a tool whose siblings are all priced.

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% and each parameter already documents its own constraints, cost multipliers, and defaults, so the baseline is 3. The model list in the description mostly restates what the schema's `model` and `ts_level` descriptions already say, and its formatting is truncated ('WhisperLargeV3: ts_level: segment') rather than adding new meaning.

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') plus the pipeline step ('Extracts audio from video and converts it to text'), so the operation is unmistakable. It does not distinguish itself from the sibling video_url_transcription, which is confusing because this tool also accepts URLs as its preferred input.

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: 'Accepts video files as URLs (preferred), data URIs, or base64 strings' tells the agent what inputs work but not when to pick this tool over video_url_transcription or audio_transcription. The model list gives useful selection guidance between Whisper variants, but that is parameter-level guidance rather than tool-level routing.

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.