Skip to main content
Glama

Audio Url Transcription Price

audio_url_transcription_price

Calculate the price for transcribing Twitter Spaces audio by providing an audio URL or duration in seconds, so you can estimate transcription costs before submitting.

Instructions

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.

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 observedv0.6.3

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it discloses that the API derives platform from the URL when a URL is given, which is genuinely useful behavior beyond the schema. It does not state that this is a non-mutating, side-effect-free price quote, nor does it mention which pricing factors (model, diarize, ts_level, include_metadata) materially change the number, leaving that entirely to the schema.

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?

Short, front-loaded, and every sentence carries a rule: purpose first, then the input-mode requirement, then the platform constraint. Minor cost: the backticked parameter fragments make it read like a schema excerpt rather than flowing prose, but nothing is wasted.

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 9-parameter pricing calculator with 100% schema description coverage and an output schema, the description covers the two things an agent cannot get from the schema alone: how the source is specified and when `platform` applies. Pricing multipliers and return shape are already structured, so nothing essential is missing.

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, but the description adds the mutual-exclusivity rule (audio_url XOR duration_seconds) and the constraint that `platform` is only meaningful alongside `duration_seconds`, otherwise inferred from the source. That is real semantic value not conveyed as a single statement in the schema.

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?

States a specific verb and resource: 'Calculate price for Twitter Spaces audio transcription', which is distinct from the transcription siblings and from generic audio_transcription_price. It does not explicitly name a sibling to distinguish itself from, so it stops short of a 5.

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 concrete input-mode guidance ('Provide either audio_url or duration_seconds') and a conditional rule for `platform`, but never says when to pick this tool over audio_transcription_price or audio_url_transcription. Usage is implied by the Twitter Spaces scoping rather than spelled out as when/when-not.

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