Skip to main content
Glama

start_batch

Begin a sequential batch transcription of untranscribed audio files. Scans folder, sorts by duration, and processes each file individually, with output validation. Returns a batch ID for progress checking.

Instructions

Start an automated sequential batch transcription of all untranscribed files in a folder. Scans for files without a matching .txt, sorts by duration (shortest first), and processes them one at a time as background jobs. Each file is validated after completion — empty or suspiciously short outputs are flagged. Batch self-advances without polling when each file finishes. Returns a batch ID to use with check_batch_progress. ⚠️ Privacy: when privacy_mode is active, one confirmation is required before the batch starts. All files then process unattended. No transcript text is returned to the API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_pathYesAbsolute Windows path to the folder.
languageNoLanguage code. Defaults to en.en
threadsNoCPU threads. Defaults to 2 of 2.
output_formatNotimestamps = with time codes (default), text = plain. Applies to all files in the batch.timestamps
privacy_modeNoOverride privacy mode for this batch. When active, requires one confirmation before batch start. All files process unattended with no transcript text returned.
Behavior4/5

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

With no annotations, the description fully discloses sequential processing, sorting by duration, validation, self-advancing, and privacy mode behavior (confirmation, unattended, no text returned). It lacks error handling details but is otherwise transparent for a batch operation.

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 (6 sentences), well-structured with a clear front-loaded action, bullet points, and emoji for emphasis. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (multi-file batch with validation), the description covers scanning, sorting, sequential processing, validation, self-advancing, and the returned batch ID for monitoring. No output schema exists, but return value is explained.

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 the schema already documents all parameters. The description adds context for privacy_mode (confirmation, no text returned) but provides minimal additional meaning for other parameters like language or threads.

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 starts an automated sequential batch transcription of untranscribed files in a folder, specifying the verb 'start batch' and resource 'files in a folder'. It distinguishes from siblings like transcribe_audio and check_batch_progress by detailing the batch process.

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 explains when to use this tool (for automated batch transcription) and includes context for privacy mode. However, it does not explicitly state when not to use it or mention alternatives like transcribe_audio for single 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