Skip to main content
Glama

transcribe_with_enhancement

Transcribe audio files using GPT-4 with enhanced outputs for detailed descriptions, storytelling narratives, professional formatting, or analytical insights.

Instructions

Transcribe audio with GPT-4 using specific enhancement prompts.

    Enhancement types:
    - detailed: Provides detailed description including tone, emotion, and background
    - storytelling: Transforms the transcription into a narrative
    - professional: Formats the transcription in a formal, business-appropriate way
    - analytical: Includes analysis of speech patterns, key points, and structure

    Args:
        input_file_name: Name of the input audio file to process
        enhancement_type: Type of enhancement to apply to the transcription
        model: The transcription model to use
        response_format: The response format
        timestamp_granularities: Optional timestamp granularities

    Returns:
    -------
        TranscriptionResult with enhanced transcription

    

Input Schema

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

Output Schema

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

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It mentions GPT-4 but doesn't disclose rate limits, authentication needs, file size constraints, processing time, or error handling. The enhancement types are listed but without operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized but not optimally structured. The enhancement types list is helpful but could be more concise. The Args and Returns sections are clear but formatted as documentation rather than natural language, making it slightly less accessible.

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

Completeness3/5

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

Given the tool's complexity (5 parameters, enhancement logic) and presence of an output schema, the description covers core functionality adequately. However, without annotations and with behavioral gaps, it doesn't fully prepare an agent for operational nuances like error cases or performance characteristics.

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 description coverage is 0%, but the description compensates well by explaining all 5 parameters in the Args section with clear meanings. It defines enhancement_type options with useful descriptions and clarifies optional vs. required parameters, adding significant value beyond the bare 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 clearly states the tool transcribes audio with GPT-4 using enhancement prompts, distinguishing it from sibling 'transcribe_audio' by specifying enhancement capabilities. It provides a specific verb ('transcribe') and resource ('audio') with clear differentiation.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'transcribe_audio' or other audio tools. The description lists enhancement types but doesn't specify scenarios where each is appropriate or when to choose this over basic transcription.

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