Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Whisper audio transcription: 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.6/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, non-destructive and non-idempotent; the description reinforces this with 'Reads or computes only and changes nothing' and 'each call is charged, so repeats are not free,' which explains the non-idempotent hint in practical terms. It adds pricing ($0.05/call, failed calls free, x402 USDC or card key) and pre-flight rejection of over-long audio — real value beyond the annotations. The only gap is return shape, partially implied by the subtitles/timestamps coverage note.

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 capability and limits, then use cases, then pricing — a sensible order with no filler sentences. It is dense and semicolon-heavy, packing price, payment methods and example URL into one long run, which costs a little scannability but nothing is redundant.

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?

With no output schema, the description still tells the agent what comes back (joined transcription, optional SRT/VTT subtitles, timed segments and words) and what limits apply. Pricing, payment routes, failure behavior and refusal rules cover everything needed to invoke this paid transcription tool correctly.

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 coverage is 100%, so the baseline is 3; the description earns a bump by clarifying cross-parameter behavior — parts are joined, so subtitles=srt/vtt and timestamps=true span the whole recording rather than per-part. It also supplies a concrete working URL example and notes the 25 MB/60-minute bound on the url parameter. The language parameter's detection default is 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 (transcribe) and resource (audio) with hard scope limits: 60 minutes, 25 MB, MP3/WAV, by URL or POST body, Whisper large-v3-turbo. It explicitly distinguishes itself from the sibling 'transcribe' by naming the short-clip case as the cheaper alternative.

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 concrete use cases (meeting notes, podcast show notes, video subtitles, interviews) and an explicit exclusion rule: 'for a short clip in any format, transcribe costs less.' It also states what is refused (longer audio) before any work runs, so the agent can avoid a doomed call.

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.