Skip to main content
Glama

Video Url Transcription Price

video_url_transcription_price

Calculate price for video URL transcription.

Quote either from a URL or from a duration. The API accepts exactly one: given a URL it derives duration and platform from the source itself, so duration_seconds and platform are rejected alongside it.


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": "video_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
platformNoSource platform: 'youtube', 'twitter', 'twitch', 'kick' or 'tiktok'. Changes the price substantially — tiktok can be ~9x youtube. 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
video_urlNoURL of video. Provide this or duration_seconds, not both. TikTok URLs cannot be quoted: use duration_seconds with platform='tiktok'
include_tsYesInclude timestamps
duration_secondsNoVideo duration in seconds, to quote without supplying a URL. Mutually exclusive with video_url
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

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does reveal genuinely behavioral facts — that the API enforces exactly-one-of URL/duration, that duration and platform are derived from a URL, and which models support diarize/ts_level — but says nothing about auth, rate limits, or pricing failure modes.

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 opening sentence is well front-loaded, but the model-list block is truncated mid-entry ('WhisperLargeV3`: ts_level: segment'), leaving an unfinished enumeration that costs space without delivering the full capability matrix.

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?

With 9 parameters at full schema description coverage and an output schema present, the description only needs to frame the quoting model and model selection, which it does. The cut-off model list is the one real completeness gap.

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 the parameters are already well documented in structured form. The description's model list and exclusivity note largely restate what the schema says, adding little meaning beyond it; baseline 3 applies.

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 video URL transcription', immediately followed by the two quoting modes (URL or duration). It does not explicitly name the sibling it differs from (video_file_transcription_price, audio_url_transcription_price), so the agent must infer the distinction from the name itself.

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?

Gives clear invocation guidance for the two mutually exclusive quote paths and warns that supplying a URL rejects duration_seconds and platform. It stops short of saying when to prefer this over the file- or audio-based price tools, so sibling routing is left to inference.

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.