Skip to main content
Glama

Video Url Transcription Price

video_url_transcription_price

Calculate transcription cost from a video URL or duration, factoring model, timestamp detail, diarization and platform pricing so you can budget a job before submitting it.

Instructions

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.

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

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully adds that a URL causes duration and platform to be derived from the source and that those two parameters are then rejected, but it never states that this is a non-mutating quote, that nothing is submitted for processing, or how the price is reported back.

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

Conciseness5/5

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

Three short sentences, front-loaded with the purpose and then the quoting constraint. No filler, and the rejection rule is placed immediately after the mode explanation where it is needed.

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?

An output schema exists, so return values need no explanation, and the 9 parameters are fully covered by the input schema. The description supplies the one interaction rule the agent must know before calling; only the non-destructive, quote-only nature of the operation is left implicit.

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 the mutual-exclusivity rules and per-parameter meaning are already fully documented in the schema. The description only restates the URL-versus-duration exclusivity and adds no detail, such as pricing multipliers or language effects, beyond what structured fields provide.

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 and resource ('Calculate price for video URL transcription'), which separates it from the file-based and audio-based pricing siblings without ambiguity. An agent can identify the tool from the first sentence alone.

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?

Explains the two quoting modes (from a URL, or from a duration) and that exactly one is accepted, which tells the agent how to choose between them. It stops short of naming sibling tools such as video_file_transcription_price or audio_url_transcription_price as alternatives for other media types.

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