Skip to main content
Glama

Video Description Price

video_description_price

Calculate the price of a video description.

Pass exactly one source: video_url, video_file or duration_seconds (with an optional platform). Use the same preset and include_metadata the job will use, since both change the price.


Available models:

  • Marlin_2B: presets: fast|balanced|detail, video≤7200s

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": {
      "model": "<model>"
    },
    "name": "video_description_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesVideo description model (e.g., 'Marlin_2B')
presetNoDetail level: 'fast', 'balanced' or 'detail'. Higher presets read small on-screen text and logos but cost more (roughly x1 / x1.7 / x3.75 machine time). Unset: 'balanced', or the cheapest preset the model offers. Ignored by models without presets
platformNoWhere the video comes from; only with duration_seconds. 'tiktok' uses a fixed price card (max 10 minutes). Omitted, the quote is for an uploaded file and can come in under a URL job's charge
video_urlNoPlatform link to quote (YouTube, Twitter/X, Twitch, Kick). TikTok links are refused: quote those by duration_seconds with platform='tiktok'
video_fileNoVideo file to quote (URL, data URI or base64); only its length is read
duration_secondsNoVideo length in seconds, to quote without a source
include_metadataNoWhether the job will ask for source metadata (flat surcharge on URL sources)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description must carry the burden, and it does disclose the key behavioral traits: a strict single-source constraint, the fact that preset and include_metadata alter the quoted price, and a capability limit (Marlin_2B supports video up to 7200s). It does not state whether the call is a pure computation with no side effects or whether authentication/balance checks apply.

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?

Two tight sentences front-load the operation and the source-selection rule, then the model note follows below a separator. The model listing is slightly ragged and truncated ('video≤7200s'), but no sentence is pure filler.

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 7-parameter pricing tool with full schema documentation and an output schema covering return values, the description supplies what the structured data cannot: the single-source rule, price-affecting inputs, and model capability bounds. Only the side-effect-free nature of a quote call and any prerequisite checks are left unstated.

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 baseline is 3, but the description adds meaning the schema cannot express: the mutual-exclusivity rule across the three source parameters and the requirement that preset/include_metadata mirror the actual job. The trailing model catalog with the ≤7200s bound further constrains model choice beyond the schema's loose 'e.g., Marlin_2B'.

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 opening sentence gives a specific verb and resource ('Calculate the price of a video description'), which cleanly separates a quote operation from the sibling execution tool video_description. It could be sharper by explicitly naming the job tool it prices, but the intent is unambiguous.

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?

It specifies a real usage rule — pass exactly one of video_url, video_file or duration_seconds, with platform only alongside duration_seconds — and warns that preset and include_metadata must match the job being priced. What it lacks is an explicit pointer to the alternative (video_description) or an exclusion statement about when not to use it.

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.