Premiere Pro MCP Server

Consolidate And Transfer

consolidate_and_transfer

Collect or transcode project media into a new Premiere project folder, confirming success only after the copied .prproj and files are present in the destination.

Instructions

Collect (copy) or transcode project media into a new project with Premiere's Project Manager. Premiere writes a Copied_ folder inside destination_path (created if missing); success is reported only after that folder holds the copied .prproj, with the copied files listed.

Input Schema

TableJSON Schema

Name	Required	Description
`transcode`	No	Transcode media to match the sequence instead of copying it (default: false)
`rename_media`	No	Rename media to match clip names (default: false)
`exclude_unused`	No	Exclude unused clips (default: true)
`convert_ae_comps`	No	Convert After Effects compositions (default: false)
`destination_path`	Yes	Destination folder path for the consolidated project
`convert_synthetic`	No	Convert synthetic importer items (default: false)
`copy_to_new_location`	No	Must be true (the default): Premiere's scripted Project Manager always collects media into the destination.
`include_all_sequences`	No	Include all sequences (default: true). If false, only active sequence is used.
`include_preview_files`	No	Include preview/render files (default: false)
`convert_image_sequences`	No	Convert image sequences to clips (default: false)

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.

Changed4 schema fields changedv1.18.6Sep 30, 2026

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

changedInput schema / properties / copy_to_new_location / description

Previous value: -"Copy media to a new location (default: true)"New value: +"Must be true (the default): Premiere's scripted Project Manager always collects media into the destination."

changedInput schema / properties / transcode / description

Previous value: -"Transcode media during copy (default: false)"New value: +"Transcode media to match the sequence instead of copying it (default: 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."

Changed2 schema fields changedv1.14.4Aug 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv1.4.0Jul 27, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.1.1May 28, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations (which only declare readOnly=false, destructive=false, idempotent=false), the description discloses concrete side effects and contract details: a Copied_<project> folder is written inside destination_path, that folder is created if missing, and success is only reported once the copied .prproj is present with files listed. This is exactly the kind of behavior an agent cannot infer from structured fields.

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 dense sentences with zero filler, front-loading what the tool does before the side-effect contract. Nothing is repeated from the title or schema.

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 described, and the description covers the write contract and success condition well. The one remaining gap is which project/sequence is the source of 'project media' (presumably the open project and, depending on include_all_sequences, the active sequence), which an agent must infer.

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 above baseline by explaining the copy-vs-transcode distinction that maps to the 'transcode' flag and by clarifying destination_path semantics (target of the Copied_<project> folder, auto-created). It still does not touch the remaining boolean flags, but they are well documented in the schema.

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 pair ('Collect (copy) or transcode') and resource ('project media into a new project') via Premiere's Project Manager, so the operation is unambiguous. It does not explicitly differentiate itself from the nearest sibling (consolidate_duplicates) or other project-level tools, keeping it just short of a 5.

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?

Usage is only implied: the copy/transcode framing suggests consolidating media for transfer or archival, but the description never states when to choose this over alternatives such as export_as_project, create_project_backup, or consolidate_duplicates, and gives no prerequisites. Adequate but leaves routing 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