Skip to main content
Glama

Video File Transcription Price

video_file_transcription_price

Calculates the transcription cost for an uploaded video file based on its duration in seconds, with optional timestamps, language, diarization, and model settings.

Instructions

Calculate price for video file transcription.

Quotes an uploaded video file by its length. For a URL use video_url_transcription_price.

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>",
      "duration_seconds": "<duration_seconds>"
    },
    "name": "video_file_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
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
include_tsYesInclude timestamps
duration_secondsYesLength of the video in seconds, which the price follows

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. 'Calculate price' plus 'price follows its length' makes clear this is a read-only estimate whose cost scales with duration, but it never states that no credits are consumed and no job is created — the distinction that matters most for a pricing endpoint.

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 lines: purpose first, the pricing rule second, the sibling redirect last. Nothing is repeated and nothing could be cut without losing routing 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 six-parameter pricing tool with a full output schema and thoroughly documented parameters, the description covers purpose and the key alternative. It leaves the preconditions (a file must already be uploaded) and the no-side-effect guarantee implicit, which are the only meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema descriptions are unusually rich (model constraints, diarize/ts_level cost multipliers, lang pitfalls), so the schema does the heavy lifting. The description's only added semantic, that price follows duration, is consistent and useful framing rather than redundant.

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 file transcription') and immediately scopes it to an uploaded file, which distinguishes it from the URL-based sibling. An agent can tell from the text alone that this is a quoting tool, not a transcription tool.

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?

Explicitly routes the URL case to video_url_transcription_price, which is the main fork an agent faces. It stops short of saying how this relates to video_file_transcription (quote first, then transcribe) or that an upload must already exist, so guidance is clear but not complete.

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