Skip to main content
Glama

Video Description

video_description

Describe what happens on screen in a video, as a timestamped index of events.

The visual counterpart of transcription: reads the picture, not the audio track (for speech use the transcription tools). Pass exactly one source: video_url for a YouTube, Twitter/X, Twitch, Kick or TikTok link, or video_file for a file.

The result is a JSON document: {"events": [{"start", "end", "description", ...}], "scenes": [...], "meta": {"duration", "preset", ...}}, with start/end in seconds. Priced on machine time, so longer videos and higher presets cost more; quote first with video_description_price. A long video can take several minutes: if the tool times out, follow up with check_job_status.


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"
  }
}

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
video_urlNoLink to a video on YouTube, Twitter/X, Twitch, Kick or TikTok; the API fetches it itself. Not for a direct link to a video file: pass that as video_file. Live streams and audio-only sources (Twitter Spaces) are rejected
video_fileNoVideo file as a direct URL to the file (preferred), data URI (data:video/mp4;base64,...) or base64 string; this server uploads it. Must contain a video stream
webhook_urlNoHTTPS URL for deAPI to call when this job finishes. Notifies your own systems; the tool still returns the result here
webhook_secretNo32-255 char key deAPI signs the callback with (HMAC-SHA256). Needs webhook_url. A secret given in chat stays in the transcript
include_metadataNoReturn the source's title, channel, upload date and view/like counts. URL sources only; carries a flat surcharge
return_result_in_responseNoReturn the description JSON inline in 'result'. Set to False for long videos to get only the download URL

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses the cost model (machine time, scaling with duration and preset), that long videos take minutes, the timeout/recovery path via check_job_status, the accepted vs rejected source types (live streams and Twitter Spaces rejected), and the exact result document shape. The only mild gap is that it never says how the job id for check_job_status is obtained, which is minor given the recovery instruction is still actionable.

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?

Front-loaded with the purpose and sibling differentiation, then source rules, then result shape, then pricing/timeout guidance, so the important routing information comes first. The appended model/preset block and the result-shape sketch are somewhat redundant with the schema and output schema, which keeps it short of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, async, priced generation tool the description covers source selection, cost drivers, timeout handling, webhook/sync return modes, and model limits. An output schema exists, yet the inline result sketch still helps the agent know what "events" and "scenes" mean without a round trip.

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 the baseline is 3, but the description adds meaning the schema does not encode: the mutual-exclusion rule that exactly one of video_url / video_file must be supplied, plus the model example (`Marlin_2B`) and its 7200s duration ceiling. The preset cost multipliers are repeated from the schema rather than added.

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?

"Describe what happens on screen in a video, as a timestamped index of events" gives a specific verb plus resource and the output form. It then explicitly contrasts itself with the transcription siblings ("reads the picture, not the audio track"), so an agent can separate it from video_url_transcription / video_file_transcription without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative for the audio case (transcription tools), states the source-selection rule ("Pass exactly one source"), routes pricing questions to video_description_price, and tells the agent what to do on timeout (check_job_status). Both conditions and alternatives are explicit rather than implied.

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.