Skip to main content
Glama

transcribe_audio

Transcribe audio to text with timestamps. Supports 13 languages, handles accents and background noise. Pay per request with Bitcoin Lightning—no signup needed.

Instructions

Transcribe audio to text with timestamps. Uses Mistral Transcription — high-accuracy speech recognition that handles accents, background noise, and overlapping speakers. 13 languages: en, zh, hi, es, ar, fr, pt, ru, de, ja, ko, it, nl. Up to 512 MB / 3 hours per file. Async — returns requestId, poll with check_job_status(jobType='transcription'), then get_job_result. 10 sats/min. Privacy: audio and transcripts are ephemeral — processed, returned, and discarded. Never persisted. Pay per request with Bitcoin Lightning — no API key or signup needed. Requires create_payment with toolName='transcribe_audio'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paymentIdYesValid payment ID (must be paid)
audioBase64YesBase64 encoded audio file
languageNoLanguage code (e.g., 'en', 'es')

Implementation Reference

  • index.js:14-45 (registration)
    The tool is registered as "transcription" (not "transcribe_audio") in the TOOLS array. The tool named "transcribe_audio" does not exist in this codebase; the closest is "transcription" listed at line 22.
    const TOOLS = [
      "image",
      "video",
      "video_from_image",
      "text",
      "vision",
      "music",
      "tts",
      "transcription",
      "3d",
      "ocr",
      "file_convert",
      "email",
      "sms",
      "call",
      "voice_clone",
      "image_edit",
      "pdf_merge",
      "epub_to_audiobook",
      "convert_html_to_pdf",
      "translate_text",
      "extract_receipt",
      "ai_call",
      "remove_background",
      "upscale_image",
      "restore_face",
      "detect_nsfw",
      "detect_objects",
      "remove_object",
      "colorize_image",
      "deblur_image",
    ];
Behavior5/5

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

With no annotations, the description fully discloses async polling, payment flow, ephemeral data, language support, file size/duration limits, and privacy. This provides comprehensive behavioral insight.

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 reasonably concise and front-loaded with purpose. Every sentence adds value, though it could be slightly tighter without losing information.

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 (async, payment, multiple languages, file limits), the description covers all essential aspects including how to retrieve results and privacy. No output schema exists, but the workflow is fully 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 baseline is 3. The description adds value by linking paymentId to create_payment and listing supported languages, but does not elaborate on audio format requirements.

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?

The description clearly states the tool transcribes audio to text with timestamps, using a specific verb and resource. It does not explicitly differentiate from sibling tools like 'transcribe_translate', but the purpose is unambiguous.

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?

The description explains when to use the tool (transcription with timestamps) and includes context on async workflow and payment. However, it lacks explicit exclusions or alternatives, leaving the agent to infer boundaries.

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/cnghockey/sats4ai-mcp-server'

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