Skip to main content
Glama

media_frames

Generate a contact sheet of source media frames at specified times or evenly spaced intervals before editing, using a temporary timeline that is removed afterward.

Instructions

Look at frames of a SOURCE media clip (before it is edited in): contact sheet at source times (seconds) or count evenly spread frames. Uses a temporary timeline that is deleted afterwards.

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": {
      "item": "<item>"
    },
    "name": "media_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
countNo
timesNo
widthNo
columnsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a meaningful side effect: it 'uses a temporary timeline that is deleted afterwards,' which tells the agent the operation is transient and self-cleaning. It also implies a read-only inspection of source media. It does not state the return form (an image contact sheet vs. frame list) or any permission/performance constraints.

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 sentences, front-loaded with the core action, and every clause adds information (scope, mode choice, temporary-timeline side effect). Minor formatting noise from the mid-sentence line break and backticked parameter names, but no wasted content.

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 5-parameter tool with no annotations and no output schema, the description covers the essential behavior and side effect but leaves layout parameters (width, columns) and the return value unexplained. An agent knows what the tool does but must guess how to control the contact sheet's shape and what it gets back.

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 coverage is 0% for 5 parameters, so the description must compensate and it only partially does: it explains `times` (in seconds, source timecodes) and `count` (evenly spread frames) and makes clear the two are alternatives. `item`, `width`, and `columns` — the latter two clearly the contact-sheet layout controls — are left entirely undocumented.

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+resource: view frames of a SOURCE media clip, with the parenthetical '(before it is edited in)' scoping it to pre-edit source media rather than timeline clips. The mention of 'contact sheet' partly overlaps the frames_contact sibling name, but the description does not explicitly distinguish the two, so sibling differentiation is left implicit.

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?

Usage is implied by '(before it is edited in)' and by naming two mutually exclusive modes (times vs. count evenly spread), which is a useful selection cue. However, there is no explicit statement of when to prefer this over frames_contact or other frame/clip tools, and no stated prerequisites.

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