Skip to main content
Glama

Build Edit Review Evidence

build_edit_review_evidence

Creates before/after contact sheets, optional bounded MP4 excerpts, and checksum receipts from rendered videos to support visual review of cuts, transitions, titles, and masks.

Instructions

Create new before/after contact sheets, optional bounded MP4 excerpts, and checksum receipts from two reviewed rendered videos. Supports visual review of cuts, transitions, titles and masks; still grids do not verify temporal behavior or authenticate host lineage.

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": {
      "before_video": "<before_video>",
      "after_video": "<after_video>",
      "before_sheet": "<before_sheet>",
      "after_sheet": "<after_sheet>",
      "operation_revision": "<operation_revision>"
    },
    "name": "build_edit_review_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
after_sheetYesNew after .png contact-sheet destination.
after_videoYesExisting rendered video captured after the edit.
before_sheetYesNew before .png contact-sheet destination.
before_videoYesExisting rendered video captured before the edit.
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.
after_review_clipNoOptional distinct new absolute after .mp4 excerpt destination; requires before_review_clip.
before_review_clipNoOptional new absolute before .mp4 excerpt destination; requires after_review_clip.
operation_revisionYesReviewed operation/snapshot revision that this evidence accompanies; declared, not host-authenticated.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
review_start_secondsNoOutput-relative excerpt start, default zero.
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.
review_duration_secondsNoBounded review excerpt duration, default three seconds.

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, and openWorld=false, but the description adds meaningful caveats: it creates new evidence files from two reviewed rendered videos, and still grids do not verify temporal behavior or authenticate host lineage. It still omits what happens if destinations already exist or how failures are reported, but the added caveats go beyond the annotations.

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, front-loaded with the action and outputs, followed by a focused limitation. Every clause earns its place and there is no redundant wording.

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 12-parameter mutation tool with nested guard objects and an output schema, the description covers purpose and key limitations but leaves usage relative to alternatives and operational failure behavior implicit. Rich schema annotations compensate, but the description itself is only minimally adequate for this complexity.

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 the schema already explains all 12 parameters in detail, including idempotency, expected CEP identity, and review excerpt bounds. The description adds only a high-level mention of before/after sheets and optional MP4 excerpts, which does not extend parameter-level meaning beyond the schema.

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 uses a specific verb ('Create') and concrete resources: before/after contact sheets, optional bounded MP4 excerpts, and checksum receipts from two reviewed rendered videos. It does not explicitly name or differentiate against siblings such as export_sequence_review_frames, so it is clear but not fully self-differentiating.

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?

It gives implied guidance by stating the tool supports visual review of cuts, transitions, titles and masks, and warns that still grids do not verify temporal behavior or authenticate host lineage. However, it never states when to prefer this over sibling review/export tools or when not to use it.

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