Skip to main content
Glama

Audio Url Transcription

audio_url_transcription

Convert Twitter Spaces audio URLs into text transcripts using Whisper models, with optional timestamps, speaker labels, and language selection. Use it to make Spaces recordings readable.

Instructions

Transcribe audio from Twitter Spaces URL to text using Whisper models.

Extracts and transcribes audio from Twitter Spaces URLs. NOTE: This endpoint only works with Twitter Spaces URLs. For video content, use video_url_transcription instead.

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": {
      "audio_url": "<audio_url>",
      "include_ts": "<include_ts>"
    },
    "name": "audio_url_transcription"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the recording as an ISO code, e.g. 'en', 'pl'. Set it whenever you know the language: auto-detection can pick the wrong one, e.g. on short or accented audio. It forces the output language, so a wrong code returns a translation instead of a transcript. Auto-detected when unset
modelNoWhisper model from the model list. Default WhisperLargeV3Ct2: honours lang, returns segments, supports diarize and word timestampsWhisperLargeV3Ct2
diarizeNoLabel who is speaking; implies include_ts. Only on models marked 'diarize' in the model list (WhisperLargeV3 rejects it). Costs 1.5x, not stacked with a finer ts_level
ts_levelNoTimestamp granularity: 'segment', 'word' or 'char'; implies include_ts. Only the levels a model lists under 'ts_level' in the model list are accepted (WhisperLargeV3: segment only). Finer than segment costs 1.5x on models that price it
audio_urlYesURL of Twitter Spaces audio to transcribe (e.g., 'https://twitter.com/i/spaces/1nAKEERkeLbKL')
include_tsYesInclude timestamps in transcription
webhook_urlNoHTTPS URL for deAPI to call when this job finishes. Notifies your own systems; the tool still returns the result here
webhook_secretNo32-255 char key deAPI signs the callback with (HMAC-SHA256). Needs webhook_url. A secret given in chat stays in the transcript
include_metadataNoInclude source metadata in the result. Carries a flat surcharge on models that price it
return_result_in_responseNoReturn transcription inline. Set to False for large files to get download URL instead

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so the description bears the behavioral burden, and it discloses only one trait: the hard input-scope restriction. It says nothing about duration, cost, or job flow, though the input schema's field descriptions already cover the pricing multipliers, webhook callback behavior, and inline-vs-download result handling.

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 scope constraint is front-loaded in the first sentence and the corrective routing is last, which is the right order. The second line ('Extracts and transcribes audio from Twitter Spaces URLs') largely repeats the opening line and could be cut.

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 an output schema present and 10 fully documented parameters, the description only needs to establish purpose and input scope, which it does decisively. An agent can call this correctly without further prose.

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 description coverage is 100% and the field descriptions are unusually rich (model capabilities, diarize/ts_level cost interactions, lang forcing translation), so the description correctly defers. It adds no parameter meaning of its own beyond the URL type constraint.

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 definition names a specific verb ('Transcribe'), a specific resource ('audio from Twitter Spaces URL') and a concrete mechanism ('using Whisper models'). It also states its narrow scope, which lets an agent separate it from the video-transcription sibling without opening 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 Guidelines4/5

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

The NOTE gives an explicit when-not ('only works with Twitter Spaces URLs') and routes video content to video_url_transcription. That is clear conditional guidance; it stops short of mentioning the file-based audio transcription path, so the routing is not fully exhaustive.

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