premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Import Folder

import_folder

Import all media files from a folder into a Premiere Pro project or bin, then read back the destination tree and report new or unverified items.

Instructions

Import the media files directly inside a folder and read the destination tree back. Refuses an unreadable baseline before importing. Reports observed new media items; unreadable or unmatched imports are committed_unverified. Host errors retain partial-change diagnostics; inspect the destination before retrying.

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": {
      "folder_path": "<folder_path>"
    },
    "name": "import_folder"
  }
}

Input Schema

Name	Required	Description
`target_bin`	No	Optional bin name or node ID to import into. Defaults to the project root.
`folder_path`	Yes	Path to the folder to 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

A3.7/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: an unreadable baseline is refused before any change, unmatched or unreadable items are committed_unverified, and host errors preserve partial-change diagnostics. This partial-failure and verification vocabulary is exactly the extra context the flat hints (readOnlyHint=false, destructiveHint=false, idempotentHint=false) cannot convey. It stops short of saying how duplicates or already-imported media are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action and then the failure semantics; almost no filler. The density of jargon ('baseline', 'committed_unverified', 'partial-change diagnostics') is left undefined, which slightly limits first-read comprehension.

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 five-parameter, nested-schema, mutation tool with an output schema and annotations, the description covers the consequential parts: precondition refusal, unverified outcomes, and partial-change recovery. Return-value shape is correctly left to the output schema, and only duplicate-handling behavior is missing.

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 folder_path, target_bin, idempotency_key and the expected_* guards are fully documented in the schema. The description only echoes 'folder' and 'destination tree' and adds nothing about bin targeting, the CEP guard, or key reuse. Baseline 3 applies.

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?

States a specific verb and resource ('Import the media files directly inside a folder') and adds a scope qualifier ('directly inside', i.e. non-recursive) plus a readback of the destination tree. This separates it from format-specific siblings like import_edl or import_image_sequence, though no sibling is named explicitly.

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 (import loose files in a folder vs. structured format importers) and gives one explicit operational rule: inspect the destination before retrying after a host error. It never states when to prefer a different import tool or what preconditions the folder must meet beyond being readable.

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

Deploy Server