Skip to main content
Glama

frames_get

Read-only

Extracts up to 12 still frames from a video asset or render at specified times so you can check framing, hooks, and cuts.

Instructions

Grab up to 12 frames (as images) from a video asset or a finished render at the given times in seconds. Use it to check framing, hooks and cuts.

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": {
      "times": "<times>"
    },
    "name": "frames_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
timesYes
widthNo
assetIdNo
renderIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe non-mutating read, and the description usefully adds the 12-frame cap, image output form, and that times are in seconds. It does not say what happens when both assetId and renderId are supplied or neither is, whether frames are returned in order, or how failures on out-of-range times are handled.

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 compact sentences with the capability and the limit (up to 12, in seconds) front-loaded, then the intended use. No filler or redundancy.

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 and 0% schema coverage, the description does a reasonable job for a small read tool: it conveys source options, the frame cap, time units, and image output. The remaining hole is the unexplained width parameter and the unstated assetId/renderId exclusivity, but the definition is otherwise sufficient to call the tool correctly.

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

Parameters3/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 carry parameter meaning, and it does partially: 'times in seconds' explains the units of the required array, and 'video asset or a finished render' maps to assetId vs. renderId. It says nothing about width (default 400, range 160-1024) and never states that the two ID parameters are alternatives — a meaningful gap left to the schema's bare property names.

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: 'Grab up to 12 frames (as images) from a video asset or a finished render at the given times in seconds.' This is concrete and distinguishes the two source types (asset vs. finished render), but it never names or contrasts a sibling tool, so the agent must infer differentiation itself.

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?

'Use it to check framing, hooks and cuts' gives a purpose-level usage cue, but there is no when-not guidance, no mention of alternatives (e.g., timeline_get or analysis_get for metadata rather than pixels), and no stated prerequisite that a render or asset must already exist.

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