Skip to main content
Glama

Extract video frames locally

extract_frames

Extract still JPEG images from a local video at specified timestamps or set intervals using local ffmpeg, with no uploads or API quota.

Instructions

Extract still images from a local video at timestamps or a fixed interval and return them as JPEG content. Runs ffmpeg locally: no upload and no API quota.

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": {
      "source": "<source>"
    },
    "name": "extract_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthNo
sourceYes
max_framesNo
timestampsNo
end_secondsNo
start_secondsNo
interval_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations were supplied, so the description carries the full behavioral burden. It usefully discloses that ffmpeg runs locally, that nothing is uploaded, that no API quota is consumed, and that output is JPEG content, which is real value. However, it is silent on precedence when both timestamps and interval_seconds are supplied, on how max_frames truncates results, and on failure modes for bad timestamps or unsupported codecs, leaving a mutation-sized gap.

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 with no filler, and the primary action is front-loaded before the environment note. The ffmpeg sentence could arguably be folded in, but nothing in the text is 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?

With no annotations and no output schema, the definition does well on execution environment and return type, which are the hardest facts to infer. It is not complete for a 7-parameter tool: width, max_frames, start_seconds, and end_seconds remain undefined, and the interaction between the two frame-selection modes is never resolved.

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 7 parameters, so the description must compensate, and it only partially does. It conveys meaning for source (a local file), timestamps, and interval_seconds, but says nothing about width, max_frames, start_seconds, or end_seconds, leaving over half the parameters undocumented anywhere.

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?

A specific verb, "Extract still images," with a clear resource, "local video," and it names the two selection modes, timestamps and fixed interval. It is distinct enough from analyze_video, video_info, and find_moments, but it never explicitly says how it differs from them, so it falls 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 definition implicitly tells the agent when the tool applies: choosing frames by explicit timestamps vs. a fixed interval. However, it gives no explicit guidance for when to use this instead of the sibling tools analyze_video or find_moments, nor does it state any exclusions or prerequisites, so the usage context is only implied.

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

Deploy Server

Other Tools