Skip to main content
Glama

transcribe_audio

Transcribe audio files to text using models like gpt-4o-mini-transcribe or gpt-4o-transcribe. Options include prompts, timestamp granularities, and various output formats.

Instructions

A tool used to transcribe audio files. It is recommended to use gpt-4o-mini-transcribe by default. If the user wants maximum performance, use gpt-4o-transcribe. Rarely should you use whisper-1 as it is least performant, but it is available if needed. You can use prompts to guide the transcription process based on the users preference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_file_nameYes
modelNogpt-4o-mini-transcribe
response_formatNotext
promptNo
timestamp_granularitiesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe transcribed text
durationNoDuration of the audio in seconds
languageNoDetected language of the audio
segmentsNoTimestamped segments
wordsNoWord-level timestamps
usageNoToken usage information
logprobsNoLog probabilities if requested
Behavior2/5

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

No annotations provided; the description only mentions model recommendations and prompt usage. It does not disclose behaviors like rate limits, data handling, or side effects.

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 short with three sentences. It is front-loaded with the core purpose, but the opening sentence is somewhat generic.

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

Completeness2/5

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

An output schema exists but is not referenced. For a tool with 5 parameters and multiple enum options, the description lacks detail on response formats and required fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description adds little value beyond the schema. Only 'prompt' is briefly mentioned; parameters like 'input_file_name', 'response_format', and 'timestamp_granularities' are not explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool transcribes audio files. The verb 'transcribe' and resource 'audio files' are specific, but it does not differentiate from sibling tools like 'transcribe_with_enhancement'.

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

Usage Guidelines3/5

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

Provides model selection guidance (default, performance, rare use) but does not address when to use this tool over alternatives like 'chat_with_audio' or 'transcribe_with_enhancement'.

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/arcaputo3/mcp-server-whisper'

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