Skip to main content
Glama

transcribe_with_enhancement

Transcribe audio files and improve transcriptions with GPT-4 enhancements including detailed, storytelling, professional, or analytical styles.

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
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 are provided, so the description must carry full burden. It discloses enhancement behavior and model usage (GPT-4), but does not mention side effects like cost, latency, authentication needs, or prerequisites (e.g., file upload). Critical operational details are missing.

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?

Description is well-structured with a summary, enhancement type list, Args, and Returns sections. It is front-loaded with purpose. Some redundancy in repeating parameter names from schema, and the 'Returns' line is vague. Overall efficient but not maximally concise.

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 5 parameters, no annotations, and a sibling transcribe tool, the description covers the main functionality and enhancement types. However, it lacks output schema details, prerequisites, and explanation of defaults (e.g., enhancement_type defaults to 'detailed'). Adequate for basic use but incomplete for nuanced decisions.

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 0%, requiring the description to add meaning. The 'Args' section gives brief explanations (e.g., 'Name of the input audio file to process'), which is adequate but not rich. With 5 parameters and enums partially conveying meaning, the description adds marginal value but does not fully compensate for the coverage gap.

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?

Description clearly states 'Transcribe audio with GPT-4 using specific enhancement prompts', specifying verb and resource, and distinguishes from siblings like transcribe_audio by adding enhancement capability. Lists four distinct enhancement types with their purposes.

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?

Implies usage when enhanced transcription is needed through the list of enhancement types, but lacks explicit guidance on when to use this tool versus the transcribe_audio sibling. No exclusions or alternatives are mentioned beyond the implied difference.

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