Skip to main content
Glama

transcribe_batch

Transcribe multiple audio/video files in a folder, reviewing each transcript before saving as .txt. Automatically skips already transcribed files and supports privacy mode.

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 start_batch instead. ⚠️ Privacy: transcript previews are processed by Claude's API. Pass privacy_mode=true to suppress previews and return metadata only. When privacy mode is active, confirmation is required before each file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threadsNoCPU threads. Defaults to 4 of 8.
languageNoLanguage code. Defaults to en.en
recursiveNoInclude subfolders. Defaults to false.
file_indexNoWhich file to process (1-based). Omit to list files first.
folder_pathYesAbsolute Windows path to the folder.
privacy_modeNoOverride privacy mode for this call. When active, requires confirmation before each file and returns metadata only.
output_formatNotimestamps = with time codes (default), text = plain.timestamps
Install Server

TDQS

A4.5/5.0
Behavior5/5

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

Despite having no annotations, the description thoroughly discloses behavior: previewing, waiting for confirmation, saving .txt files next to sources, skipping already transcribed files, supported formats, and privacy mode effects. This exceeds typical transparency expectations.

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?

The description is relatively lengthy but well-structured, with each sentence adding value (formats list, alternative tool, privacy warning). It is not overly verbose, but could be tightened slightly by moving the format list to an appendix.

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 no output schema, the description covers the workflow (preview, confirmation, saving, skipping) and privacy considerations. However, it does not describe what the tool returns besides 'metadata only' in privacy mode, leaving a minor gap for interactive completion behavior.

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 baseline is 3. The description adds context for privacy_mode (suppress previews, return metadata) but does not materially enhance understanding of other parameters beyond the schema's own 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?

The description clearly states the tool transcribes multiple audio/video files in a folder, with specific behavioral details (one file at a time, preview, confirmation). It also distinguishes itself from the sibling tool start_batch, making its purpose unambiguous.

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 instructs when to use this tool vs. an alternative: 'For large unattended batch jobs, use start_batch instead.' Also describes interactive context and privacy mode behavior, giving clear usage direction.

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

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