Skip to main content
Glama
Sign In
premiere-pro-mcp

premiere-pro-mcp

by matt-j-penny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Diff Sequence Snapshots

diff_sequence_snapshots
Read-onlyIdempotent

Compares two sequence snapshots to report added, removed, moved, trimmed, retimed, enabled, and renamed clips with frame deltas, per-track counts, and EDL-style timecode lines.

Instructions

Diff two sequence snapshots (from get_sequence_structure or inspect_sequence_structure_uxp) into added, removed, moved, trimmed, retimed, enabled, and renamed clip changes with frame deltas, per-track counts, and EDL-like timecode lines. Local-only; never reads or changes Premiere.

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": "<before>",
      "after": "<after>"
    },
    "name": "diff_sequence_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterYesLater sequence snapshot.
beforeYesEarlier sequence snapshot.
frame_rateNoFrame rate override for frame math and timecodes (1..240). Defaults to the snapshot frame rate or 30.
tolerance_framesNoDeltas of at most this many frames count as unchanged (default 0).
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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, so the safety profile is covered. The description nonetheless adds useful context: it explicitly says it is local-only and never reads or changes Premiere, which matters because the schema carries CEP/UXP guard parameters (expected_cep_target, expected_project_path) that an agent might otherwise assume require a host connection. It does not discuss mismatched frame rates or invalid-snapshot behavior.

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 tight sentences, front-loaded with the diff action and its output categories, closing with the locality constraint. No filler and no repetition of the title.

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 an output schema and full annotations present, the description only needs to cover input provenance and scope, and it does both. Minor gaps remain around behavior when the two snapshots disagree on frame rate or track shape, but nothing essential for a correct call is missing.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by identifying the provenance of the before/after snapshot objects, which is the one thing the deeply nested schema cannot convey on its own. It still says nothing about frame_rate override or tolerance_frames semantics, leaving those to the 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?

States a specific verb+resource ("Diff two sequence snapshots") and enumerates exactly what categories of change are produced — added, removed, moved, trimmed, retimed, enabled, renamed — plus the output form (frame deltas, per-track counts, EDL-like timecode lines). That is far more specific than the title and clearly separates it from sequence-inspection siblings.

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?

Names the exact producers of the input data (get_sequence_structure or inspect_sequence_structure_uxp), which tells an agent the required workflow: capture a snapshot, capture another, then diff. It does not state any when-not condition or name a competing comparison tool, so it falls short of a 5.

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