Skip to main content
Glama

Generate Media Contact Sheet

generate_media_contact_sheet

Creates a disk-verified PNG contact sheet from evenly sampled frames of a local video, with configurable grid and thumbnail size. Refuses to overwrite existing output and never modifies Premiere or source media.

Instructions

Generate a new, disk-verified PNG contact sheet from evenly sampled source frames. Refuses to overwrite an existing output and does not modify Premiere or the source.

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": {
      "media_path": "<media_path>",
      "output_path": "<output_path>"
    },
    "name": "generate_media_contact_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNoGrid rows from 2 through 8 (default: 3)
columnsNoGrid columns from 2 through 8 (default: 4)
media_pathYesExisting local video file
output_pathYesNew .png output path
idempotency_keyNoOptional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
thumbnail_widthNoThumbnail width from 160 through 1280 pixels (default: 320)
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare the coarse safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds genuinely new behavior: the output is disk-verified, an existing file is refused rather than replaced, and neither the Premiere project nor source media is modified, which reconciles the write with destructiveHint=false.

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, no filler, with the produced artifact and the sampling approach front-loaded and the safety constraints following. Every clause carries information an agent needs before invoking.

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 a rich 100%-covered schema, an output schema, and annotations supplying the safety profile, the description only needs to cover side effects and failure behavior, which it does for the overwrite case. The CEP identity guard and idempotency/replay semantics are left entirely to the schema, a minor gap given the tool's eight parameters and nested guard object.

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 100%, so every parameter including the nested expected_cep_target and the idempotency_key already carries detailed documentation. The description adds only the notion of even sampling, which loosely relates to rows/columns but supplies no new per-parameter meaning, matching the baseline for a fully documented schema.

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?

The description names a specific verb and artifact: a PNG contact sheet generated from evenly sampled source frames, written to disk. It also scopes what it does not touch (Premiere, the source media), which lets an agent separate it from adjacent media-inspection siblings like inspect_media_streams.

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 the artifact produced and by the hard constraint that an existing output will not be overwritten, which tells the agent to pick a fresh output_path. However, no explicit when-to-use/when-not guidance or named alternative is given, so the agent must infer the boundary cases itself.

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