Skip to main content
Glama

Sample frames across a clip

sample_frames
Read-only

Extract evenly spaced or exact-timestamp video frames as separate images to review pacing, check continuity, read on-screen text, or describe scenes.

Instructions

Return several frames as separate images — evenly spaced across the clip (or a range), or at the exact times you list. Use it to review pacing, check continuity, read on-screen text, or describe what happens in a video. For a single overview image, contact_sheet is cheaper.

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

Input Schema

NameRequiredDescriptionDefault
endNoOnly look up to this time.
pathYesAbsolute path to a local video file. ~ is expanded.
countNoEvenly spaced frames to return (ignored if times is given).
startNoOnly look from this time on.
timesNoExact timestamps to grab instead of evenly spaced ones.
max_widthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description's disclosure that the output is multiple separate images (not a single composite) and that contact_sheet is the cheaper option adds real behavioral context. It stops short of noting the frame-count ceiling or resolution tradeoffs, but the key cost/output-shape traits are covered.

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 sentences, both load-bearing: the first defines the behavior and its modes, the second gives use cases and the cheaper alternative. Front-loaded with no filler or restatement of the title.

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?

With no output schema, the description still communicates the return shape ('several frames as separate images'), which is the most important thing an agent needs. Some gaps remain around why start/end are ignored when times is supplied and any resolution guidance, but nothing critical for correct invocation is missing.

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 83%, so the baseline is 3, and the description earns a bump by clarifying that count applies to evenly spaced frames while 'times' overrides it with exact timestamps, and that start/end define an optional range. Only max_width is left entirely to the schema, which already documents it adequately.

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?

States a specific verb and resource (return several frames as separate images) and names the two operating modes: evenly spaced across the clip or a range, or exact listed times. It also implicitly separates this tool from grab_frame/extract_frames by emphasizing 'several' and from contact_sheet by contrast, so an agent can place it without opening a 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?

Gives concrete use cases (review pacing, check continuity, read on-screen text, describe what happens) and names an alternative with the condition that selects it: 'For a single overview image, contact_sheet is cheaper.' That is explicit when-to-use plus when-to-use-something-else.

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