Skip to main content
Glama

Agent Data Tools: Speech to text and text to speech

Transcribe long audio: up to 60 minutes of MP3 or WAV, with subtitles

transcribe_long
Read-only

Transcribe a podcast, meeting, interview or lecture: up to 60 minutes of MP3 or WAV (25 MB) by URL or uploaded in a POST body, 90+ languages, Whisper large-v3-turbo. Parts are joined, so subtitles=srt or vtt and timestamps=true cover the whole recording; longer audio is refused before anything runs. Use for meeting notes, podcast show notes, video subtitles and interviews; for a short clip in any format, transcribe costs less. Example: url=https://upload.wikimedia.org/wikipedia/commons/7/77/Tofino_pronunciation.mp3. Price $0.05/call via x402 USDC or a card key (/credits); failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "transcribe_long"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of an MP3 or WAV file (max 25 MB, 60 minutes); or POST the file itself (raw body, multipart `file` part, or base64 in JSON)
languageNoSpoken language code such as en, sv or de (default: detected per part)
subtitlesNosrt or vtt: also return subtitle text for the whole recording
timestampsNotrue: also return timed segments and words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Adds substantial facts beyond the annotations: pricing ($0.05/call), failed calls free, repeats charged, payment paths (x402 USDC or card key), and that oversized audio is refused before anything runs. However, 'Reads or computes only and changes nothing' merely restates readOnlyHint, and the description never states rate limits or latency for a 60-minute job. Good added context, some redundancy.

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?

Front-loaded with the core capability and limits, then use cases, example, and pricing in a sensible order with no filler sentences. It is a dense single paragraph though, with pricing and payment detail packed in, and the 'reads or computes only' clause could be dropped entirely.

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 read-only transcription tool with no output schema, it covers the essentials an agent needs: input forms, size/duration ceiling, refusal behavior, what subtitles and timestamps return, and the cost model. Payment/auth requirements are disclosed, which is the main thing annotations cannot express.

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 does add real meaning by explaining that joined parts make subtitles=srt/vtt and timestamps=true cover the whole recording, and it gives a working url example. Still, the language parameter and the POST-body upload variants are left entirely to 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?

States a specific verb and resource ('Transcribe a podcast, meeting, interview or lecture'), then pairs concrete scope limits (60 minutes, 25 MB, MP3/WAV) and the underlying model (Whisper large-v3-turbo). It explicitly distinguishes itself from the sibling 'transcribe' for short clips in any format, so an agent can pick correctly without reading either schema.

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

Usage Guidelines5/5

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

Gives named use cases (meeting notes, podcast show notes, video subtitles, interviews) and an explicit alternative with the selecting condition: 'for a short clip in any format, transcribe costs less.' The length cap refusal behavior also tells the agent when this tool is the wrong pick.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.