Premiere Pro MCP Server

Compare Cmx3600 Edls

compare_cmx3600_edls

Compare two CMX 3600 EDLs by event number to identify added, removed, and changed editorial events without modifying either file or Premiere.

Instructions

Compare two local CMX 3600 EDLs by event number and report bounded added, removed, and changed editorial events. Read-only; it does not alter either interchange file or Premiere.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`after_path`	Yes	Existing revised .edl file
`before_path`	Yes	Existing baseline .edl file

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.18.6Sep 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / properties / data / description

Previous value: -"Tool-specific result data when ok is true."New value: +"Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it."

Addedv1.14.4Aug 29, 2026

TDQS

B3.4/5.0

Behavior1/5

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

The description asserts 'Read-only; it does not alter either interchange file or Premiere,' but the annotations declare readOnlyHint=false. This directly contradicts the structured safety signal, leaving an agent unable to trust which is correct and creating the exact ambiguity annotations exist to prevent.

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: what it does first, then the safety claim. No filler, no repetition of the tool name, and the operationally important scoping detail is front-loaded.

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?

An output schema exists so return values need not be spelled out, and the description still summarizes the report shape (added/removed/changed events). The only shortfall is that the read-only/no-alteration claim conflicts with annotations rather than resolving behavior.

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 100% and both parameters are documented in the schema (baseline/revised .edl paths). The description adds only the 'local' constraint and the comparison key ('event number'), which is marginal value over an already-complete 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?

Specific verb (compare) plus resource (two local CMX 3600 EDLs) and the matching key (event number), with the output named ('bounded added, removed, and changed editorial events'). It is instantly distinguishable from siblings like inspect_cmx3600_edl and validate_cmx3600_edl, which operate on a single EDL.

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?

The description implies usage ('compare two local CMX 3600 EDLs') but never states when to pick this over the sibling inspect/validate/import EDL tools, nor any prerequisite such as both files existing locally. Implied context only, not explicit guidance.

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

Deploy Server