Skip to main content
Glama

frame_preview

Render a timeline frame at a specified time or the playhead as an image, saving a full-resolution PNG so you can visually verify edits, titles, grades, and composites.

Instructions

Render the timeline frame at time (default: playhead) as an image you can see — use it to verify edits, titles, grades and composites. Full-resolution PNG is kept in ~/Documents/ResolveMCP/previews.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "frame_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNo
widthNo
keep_playheadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses that an image is rendered and that a full-resolution PNG is saved to a specific path, but it does not explain whether the playhead is moved or restored, what keep_playhead does, or whether existing preview files are overwritten.

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?

The description is two compact sentences with the core action, usage context, and output location front-loaded. There is no filler or unnecessary repetition.

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?

For a three-parameter rendering tool with no output schema, it adequately explains the visible output and on-disk PNG location. It remains incomplete on two parameter behaviors and on whether rendering affects the playhead, which is important given the keep_playhead option.

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%, so the description must compensate. It explains only that time defaults to the playhead; width and keep_playhead are left unexplained, even though keep_playhead implies meaningful side-effect behavior.

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?

The description states a specific verb and resource: render the timeline frame at a given time as an image. It clearly explains the practical purpose (verifying edits, titles, grades and composites), but it does not explicitly distinguish itself from related tools such as frames_contact or playhead.

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

Usage Guidelines4/5

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

It gives clear usage context: verify edits, titles, grades and composites. It does not state when not to use it or name an alternative tool, so it stops short of full when/when-not guidance.

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