Skip to main content
Glama

video_frames

Extract frames from a video by count, interval, or timestamps, plus an optional contact sheet, to inspect with Read.

Instructions

Extract video frames (count, every_s or timestamps) + contact sheet, to view with Read.

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": {
      "path": "<path>"
    },
    "name": "video_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
countNo
widthNo
formatNo
every_sNo
out_dirNo
timestampsNo
contact_sheetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false, so the description carries most of the burden. It adds that a contact sheet can be generated and that output is meant for the Read tool, which is useful, but it never says that files are written to disk, where they land (out_dir default), or how they are named.

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?

A single compact sentence with the core action front-loaded and the parameter hints parenthesized. It is efficient, though the extreme terseness contributes to the missing parameter and output detail.

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?

With 8 parameters, 0% schema coverage, and no output schema, the description is thin. An agent can call the tool, but must guess at width, format, out_dir behavior, and whether count/every_s/timestamps can be combined, which is a meaningful gap for a file-producing tool.

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 description coverage is 0%, so the description must compensate for 8 parameters. It explains four of them (count, every_s, timestamps, contact_sheet) and groups the frame-selection ones meaningfully, but leaves width, format, and out_dir completely unexplained, so the coverage gap is only partly closed.

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 verb and resource ("Extract video frames") and names the three selection modes plus the contact-sheet option, so the agent knows exactly what the tool produces. It does not explicitly contrast itself with the sibling "extract", so it stops short of a 5.

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?

The clause "to view with Read" implies the downstream workflow, and "(count, every_s or timestamps)" signals that these are alternative selection strategies. There is no explicit when-not guidance, no statement about mutual exclusivity or precedence if several are supplied, and no routing to sibling tools.

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