Skip to main content
Glama

start_batch

Start sequential batch transcription of untranscribed files in a folder. Skips completed files, processes shortest first, and flags invalid outputs.

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
threadsNoCPU threads. Defaults to 4 of 8.
languageNoLanguage code. Defaults to en.en
folder_pathYesAbsolute Windows path to the folder.
privacy_modeNoOverride privacy mode for this batch. When active, requires one confirmation before batch start. All files process unattended with no transcript text returned.
output_formatNotimestamps = with time codes (default), text = plain. Applies to all files in the batch.timestamps
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses scanning logic, sorting by duration, sequential background execution, post-completion validation, self-advancing behavior, return of a batch ID, and privacy-mode confirmation. This is exceptionally transparent.

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 a single paragraph of five sentences, front-loaded with the primary purpose. Every sentence adds valuable detail—scanning, sorting, validation, self-advancing, and privacy—while remaining efficient. No redundant or filler content.

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?

For a complex batch tool with no output schema, the description covers all essential operational aspects: what it does, how it processes files, validation feedback, automatic advancement, return value, and privacy behavior. It even points to the companion check_batch_progress tool. This is complete for agent decision-making.

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%, giving a baseline of 3. The description adds meaningful context for privacy_mode, explaining the one-time confirmation and that no transcript text is returned. It also clarifies that output_format applies to all files in the batch, which is absent from the schema.

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 starts with a specific verb+resource: 'Start an automated sequential batch transcription of all untranscribed files in a folder.' It clearly distinguishes itself from sibling tools by detailing the batch scanning, sorting, and background processing behavior. It also references check_batch_progress, reinforcing its unique role.

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 provides clear context: use when you need to transcribe all untranscribed files in a folder sequentially as background jobs. It does not explicitly state when not to use it or mention alternative tools, but the context is strong enough to guide the agent.

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