Skip to main content
Glama

transcribe_batch

Transcribe audio and video files in a folder one by one, previewing each transcript before saving as .txt. Skips files with existing transcripts.

Instructions

Transcribe multiple audio/video files in a folder interactively, one file at a time. Shows a preview of each transcript and waits for confirmation before continuing. Saves each transcript as a .txt file next to its source. Files already transcribed (with matching .txt) are shown as done and skipped. Supported formats: mp3, wav, mp4, mkv, avi, mov, webm, m4a, flac, ogg. NOTE: For large unattended batch jobs, use whisper-cli.exe directly from the command line — see TROUBLESHOOTING.md for the command syntax.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_pathYesAbsolute Windows path to the folder.
file_indexNoWhich file to process (1-based). Omit to list files first.
languageNoLanguage code. Defaults to en.en
threadsNoCPU threads. Defaults to 2 of 2.
recursiveNoInclude subfolders. Defaults to false.
Behavior4/5

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

No annotations, so description carries full burden. Describes interactive behavior, preview, confirmation, skip logic, and supported formats. Could add error handling or return value details.

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?

Two efficient sentences that front-load core purpose, then add important details and alternative tool info. No wasted words.

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?

Covers key aspects: purpose, usage guidelines, behavioral details, supported formats. Missing return value description, but no output schema to cover that. Adequate for tool selection and invocation.

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 schema already documents all parameters. Description adds minimal extra context beyond the schema descriptions.

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?

Clearly describes transcribing multiple files interactively with preview and confirmation. Distinguishes from sibling tools by noting alternative for unattended batches.

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

Usage Guidelines5/5

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

Explicitly states when to use (interactive folder batch) and when not (large unattended jobs, pointing to whisper-cli). Also mentions skipping already transcribed files.

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