Skip to main content
Glama

Video Description Price

video_description_price

Calculate the price of a video description job from a video URL, file, or duration, including the preset and metadata options planned for the job so the quote matches the final charge.

Instructions

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.

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

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations present, the description must carry the behavioral load, and it does communicate one important trait: the quote is parameter-sensitive, so a mismatched preset or include_metadata yields a wrong price. It says nothing about whether the call is side-effect free, whether it consumes credit, or whether quotes expire, which are the traits an agent would want 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?

Two tight sentences with the core constraint ('exactly one source') front-loaded and the accuracy caveat second. No filler and nothing an agent must read past to find the operative rule.

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 a full output schema and fully documented parameters, the description plus schema covers everything needed to get a correct quote. The one loose thread is that it never confirms the call itself is free and non-mutating, which matters more here than return-value detail given the output schema exists.

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% and the descriptions already explain enum meanings, the TikTok refusal, and the upload-vs-URL price difference, so the schema does the heavy lifting. The description does contribute one constraint the schema cannot express, the exactly-one-source requirement, but otherwise mostly restates existing parameter meaning.

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 first sentence names a specific verb and resource ('Calculate the price of a video description'), which cleanly separates it from the sibling video_description job tool and from the other *_price siblings by resource. It stops short of explicitly naming video_description as its companion, so the pairing is implied rather than stated.

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 gives concrete pre-call conditions: supply exactly one of video_url / video_file / duration_seconds, and mirror the preset and include_metadata that the actual job will use because both affect price. That is real when/how guidance, though it never explicitly says 'call before video_description' or addresses when a quote is unnecessary.

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