Skip to main content
Glama

Audio Url Transcription Price

audio_url_transcription_price

Calculate price for Twitter Spaces audio transcription.

Provide either audio_url or duration_seconds for price calculation. platform is only accepted alongside duration_seconds; with a URL the API derives the platform from the source.


Available models:

  • WhisperLargeV3Ct2: ts_level: segment|word, diarize, output=json (text + segments)

  • WhisperLargeV3: ts_level: segment

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

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
platformNoPass 'twitter' when quoting a Twitter Spaces recording by duration_seconds, so it is priced as a platform source. Only valid together with duration_seconds
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_urlNoTwitter Spaces URL (required if duration_seconds not provided)
include_tsYesInclude timestamps
duration_secondsNoAudio duration in seconds (required if audio_url not provided)
include_metadataNoInclude source metadata. Carries a flat surcharge on models that price it

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden alone. It implies a non-mutating price quote and discloses that the API derives platform from the URL, but it never states that no charge or job is created, nor anything about rate limits or failure modes for an invalid URL.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence and the either/or rule are well front-loaded, but the trailing model list duplicates schema content and ends abruptly at 'ts_level: segment', leaving a truncated thought that costs tokens without adding reliable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter pricing tool with a full output schema and 100% schema coverage, the description covers the core contract: what is priced, the two mutually exclusive input modes, and the platform constraint. Remaining gaps (no-charge semantics, what the price response contains) are modest given the output schema already exists.

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%, so parameter meaning is already fully documented in the schema, and the description largely restates it (the either/or rule, the platform-with-duration rule). The model capability list adds some routing help, but it duplicates the `model` schema description and is cut off mid-entry.

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 opens with a specific verb and resource: 'Calculate price for Twitter Spaces audio transcription.' The platform specificity plus the '_price' framing lets an agent distinguish it from the plain transcription tools, though it never names the generic audio_transcription_price sibling as the alternative for non-Twitter audio.

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?

It gives clear input-mode guidance ('Provide either audio_url or duration_seconds') and a conditional constraint for `platform`, which is real usage direction. But it never says when to pick this tool over audio_transcription_price or audio_url_transcription, so the tool-selection decision is left to inference from the name.

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.