premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Validate Cmx3600 Edl

validate_cmx3600_edl

Validates a local CMX 3600 EDL for supported event grammar, timecodes, durations, duplicate event IDs, record overlaps, and gaps before Premiere interchange.

Instructions

Validate a local CMX 3600 EDL's supported event grammar, timecodes, durations, duplicate event IDs, record overlaps, and record gaps before user-assisted Premiere interchange.

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": {
      "path": "<path>"
    },
    "name": "validate_cmx3600_edl"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Existing local .edl file
`frame_rate`	No	CMX timecode rate: 24, 25, 29.97, 30, 50, 59.94, or 60 (default: 24)
`idempotency_key`	No	Optional 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.
`expected_cep_target`	No	Optional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
`expected_project_path`	No	Optional 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

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.
`receipt`	No	Versioned common mutation receipt; success never implies rendered verification.
`idempotency`	No	Present 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.

First observedv1.30.0Nov 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, which is a counterintuitive profile for a validator, and the description does not reconcile this (e.g. whether the EDL file is ever rewritten or only reported on). It does add useful scope information by calling the file "local" and by pairing validation with the downstream interchange step. Output structure is covered by the output schema, so no credit is needed there.

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?

A single sentence with the purpose, the enumerated checks, and the usage context front-loaded in that order. Every clause carries information and there is no filler.

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?

For a validator with a rich, fully documented five-parameter schema and an output schema, the description covers what is checked and when it is used, which is the essential payload. The remaining gap is behavioral: it never states that the EDL is not modified, which matters given readOnlyHint=false.

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 path, frame_rate, idempotency_key, and the nested guard objects are already fully documented in the schema. The description adds no semantics for the supported frame rates or for why an idempotency key applies to a validation call. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb ("Validate") and resource ("a local CMX 3600 EDL") and enumerates the exact checks performed: event grammar, timecodes, durations, duplicate event IDs, record overlaps, and record gaps. This goes well beyond the tautological title. It stops short of explicitly contrasting with the sibling tools inspect_cmx3600_edl and compare_cmx3600_edls, so the agent must infer the boundary itself.

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?

"Before user-assisted Premiere interchange" gives one clear usage moment, which is real context. There is no when-not guidance and no routing to the obvious alternatives (inspect_cmx3600_edl for reading, compare_cmx3600_edls for diffing), so selection among them is left to inference.

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

Deploy Server