Skip to main content
Glama

transcribe_audio

Transcribe audio or video files into text, timestamps, JSON, or SRT subtitles using Whisper on Windows. Supports MP3, WAV, MP4, MKV, and more — automatically converts via FFmpeg.

Instructions

Transcribe a single audio or video file using whisper.cpp on Windows. Natively supports mp3 and wav. Automatically converts mp4, mkv, avi, mov, webm, m4a, flac, ogg etc. via FFmpeg — no manual conversion needed. Can output plain text, timestamps, JSON, or SRT subtitle files. For files that may take more than 4 minutes, set background=true to run as a detached job and use check_progress to monitor it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesAbsolute Windows path, e.g. C:\Users\You\Downloads\recording.mp4
modelNoOverride model path. Leave blank to use active model.
languageNoLanguage code (e.g. en, ja, es, fr) or 'auto' to detect automatically. Defaults to en.en
output_formatNotext = plain (default), timestamps = with time codes, json = structured, srt = subtitle file saved next to source.text
threadsNoCPU threads. Defaults to 2 of 2.
save_to_fileNoSave transcript as .txt next to the source file.
backgroundNoRun as a detached background job. Returns a job ID immediately. Use check_progress to monitor. Recommended for files over 10 minutes.
temperatureNoSampling temperature 0.0–1.0. Default 0.0 (deterministic). Higher values reduce hallucination on noisy audio at the cost of consistency.
promptNoPrior context string injected before transcription. Improves accuracy for domain-specific vocabulary, speaker names, or technical terms. Example: 'Names: Keemstar, DramaAlert.'
condition_on_prev_textNoRe-enable conditioning each segment on its own prior output (removes --max-context 0 flag). Default false (off). Only enable for highly structured audio where context continuity helps.
no_speech_tholdNoConfidence threshold below which segments are treated as silence rather than transcribed. Default 0.6.
beam_sizeNoBeam search width. Higher = more accurate but slower. Default 5.
best_ofNoNumber of candidate sequences to evaluate. Default 5.
gpu_deviceNoGPU device index for multi-GPU systems. Use check_system to see available GPUs. Default 0.
processorsNoNumber of parallel processors for chunk processing. Default 1.
word_timestampsNoOutput one word per timestamped segment (sets --max-len 1 --split-on-word). Useful for clip alignment and precise timecode search.
max_segment_lengthNoMaximum segment length in characters. Controls line break frequency in output. Ignored when word_timestamps=true.
split_on_wordNoSplit segments at word boundaries rather than mid-word. Defaults to false.
diarizeNoStereo speaker diarization — labels left/right channel speakers in transcript. Requires stereo audio with speakers on separate channels.
vad_modelNoAbsolute path to a Silero VAD model .bin file. When provided, voice activity detection strips silence before transcription — reduces hallucinations and speeds up processing. Download via download_model.
offset_tNoStart transcription at this offset in milliseconds. Use to process a specific section of a file.
durationNoProcess only this many milliseconds of audio starting from offset_t (or the beginning). Use with offset_t to target a specific time window.
Behavior4/5

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

With no annotations, the description covers key behaviors: auto-conversion via FFmpeg, output formats, background job capability, and effect of parameters like temperature. It could mention resource usage or error handling but is sufficient for most contexts.

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?

The description is concise: four sentences front-loaded with core purpose, no fluff, and efficiently conveys essential information without redundancy.

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?

Given 22 parameters and full schema coverage, the description explains overall workflow (input handling, output options, background mode) and references sibling tools. It lacks explicit error/return details but is otherwise comprehensive.

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 coverage is 100%, so baseline is 3. The description adds value beyond schema with context like automatic conversion, background job behavior, and usage tips (e.g., for duration and offset). This justifies a 4.

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?

The description clearly states the tool transcribes a single audio/video file using whisper.cpp on Windows, lists supported formats and conversion, and contrasts with batch/analyze siblings through naming context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description advises when to use background mode for long files and references check_progress for monitoring. It implies single-file use vs batch but does not explicitly exclude alternatives or state when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eviscerations/whisper-windows-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server