Skip to main content
Glama

Watch

media_downloader_watch

Downloads a video with captions and extracts scene-change key frames, returning a bundle manifest that flags missing media, transcript, or frames for partial-result handling.

Instructions

Download a video with its captions and extract scene-change key frames.

Returns the bundle manifest: the media, the transcript, the key frames, and whatever could not be obtained. status is success only when both captions and frames are present, so a caller can surface a partial result before reasoning over an incomplete bundle. A degraded run never raises.

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": {
      "link": "<link>"
    },
    "name": "media_downloader_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYes
max_framesNo
min_framesNo
subtitle_langsNo
scene_thresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.4.7

TDQS

B3.4/5.0
Behavior4/5

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

Goes beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) by disclosing the return manifest shape, the `status` success/partial semantics, and the important trait that a degraded run never raises. That failure-mode disclosure is exactly the kind of thing annotations cannot convey; it stops short of covering on-disk artifacts or network/permission constraints.

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 core action, then return contract and edge-case behavior. Four sentences, each carrying information, with no filler; the double-backtick emphasis on `status`/`partial` is slightly verbose but not wasteful.

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

Completeness3/5

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

Return semantics are well covered despite no output schema, and the non-raising guarantee is valuable. However, for a five-parameter tool with zero schema documentation, the description leaves the agent unable to set frame limits, language preferences, or scene sensitivity correctly.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, and the description adds no meaning to `link`, `max_frames`, `min_frames`, `subtitle_langs`, or `scene_threshold`. It only obliquely implies captions and scene-based frame extraction, so an agent gets no guidance on tuning frame counts or thresholds.

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?

States a specific compound action: download a video with captions and extract scene-change key frames. Clear verb+resource. It doesn't differentiate itself from siblings like media_downloader_download_video, download_media, or watch_media, so an agent must infer that this is the combined media+transcript+frames pipeline.

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

Usage Guidelines3/5

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

Usage is only implied: a caller wanting media, transcript, and key frames together should use this, and can tolerate a partial bundle. There is no explicit 'use this instead of X' or precondition statement, despite three plausible overlapping siblings.

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