premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Import Edl

import_edl

Blocks unsafe CMX 3600 EDL imports that hang the Premiere UI; convert the EDL to FCP7 XML and use import_fcp_xml instead for unattended interchange.

Instructions

Unavailable by design: CMX 3600 EDL import opens Premiere UI that can block the CEP bridge. No import is attempted; convert the EDL to FCP7 XML and use import_fcp_xml for unattended 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": {
      "file_path": "<file_path>"
    },
    "name": "import_edl"
  }
}

Input Schema

Name	Required	Description
`file_path`	Yes	Absolute path to the CMX 3600 .edl file that was requested for import.
`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

A4.4/5.0

Behavior4/5

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

The description adds the failure mode that annotations cannot express: the UI-blocking CEP bridge hazard that motivates the refusal. The one gap is that it never says what a caller actually receives when invoking it anyway (an error payload vs. a silent no-op), and the annotations (readOnlyHint=false, idempotentHint=false) imply a mutating, non-repeatable operation while the description says nothing is applied — a mild inconsistency that is conservative rather than dangerous.

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, zero waste, with the blocking fact front-loaded before the remedy. Nothing could be removed without losing either the reason or the routing instruction.

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 deliberately disabled tool with a rich nested schema and an output schema, the description supplies what matters: why it is off and where to go instead. The only shortfall is the absence of the call outcome for a caller who tries it anyway, which would remove the last guesswork.

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%, so file_path, idempotency_key and expected_cep_target are already fully documented in the schema. The description adds nothing about any parameter, which is the correct baseline 3 when the schema carries the load, though it leaves the idempotency_key semantics entirely to the schema even though a refusing tool makes them moot.

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 opens with 'Unavailable by design' and then names the exact resource and reason (CMX 3600 EDL import opens Premiere UI that can block the CEP bridge). It also names the sibling that should be used instead (import_fcp_xml), so an agent can distinguish this tool from export_sequence_edl and validate_cmx3600_edl without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-not ('No import is attempted') plus a concrete alternative path: convert the EDL to FCP7 XML and call import_fcp_xml for unattended interchange. There is no ambiguity about whether to call this tool.

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

Deploy Server