Premiere Pro MCP Server

Consolidate And Transfer

consolidate_and_transfer

Copies and consolidates a Premiere project's media into a specified folder, with options to transcode or exclude unused clips, and confirms success only when the copied project is present.

Instructions

Consolidate, copy, or transcode project media using the Project Manager. Reports success only after a new destination folder contains a copied Premiere project.

Input Schema

TableJSON Schema

Name	Required	Description
`transcode`	No	Transcode media during copy (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	Copy media to a new location (default: true)
`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.
`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.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

B3.4/5.0

Behavior3/5

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

The description adds a useful behavioral guarantee: success is reported only after a new destination folder contains a copied Premiere project. Annotations already signal non-read-only and non-destructive intent. However, it does not disclose whether the source project is modified, whether the operation is long-running, or what happens on failure.

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 with the core action front-loaded and the key success condition second. No fluff, no repetition of schema details. Every sentence earns its place.

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?

Given a rich input schema and an output schema, the description provides the essential behavioral contract. It could mention prerequisites or failure handling, but the success criterion compensates for much of that gap. The tool is adequately specified for an agent to invoke it confidently.

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?

All 10 parameters are fully documented in the schema, so the description carries little parameter burden. The high-level mention of consolidate/copy/transcode maps loosely onto the boolean flags, but no parameter-specific meaning is added beyond 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 clearly states the operation: consolidate, copy, or transcode project media via the Project Manager. It names the resource and adds a concrete success condition. It does not explicitly differentiate from sibling tools like export_as_project or consolidate_duplicates, but the Project Manager framing provides enough distinction.

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

Usage Guidelines2/5

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

The description implies the tool is for consolidating/transferring project media but gives no explicit guidance on when to use it versus alternatives, and no prerequisites such as saving the project or ensuring destination availability. Without exclusions or conditions, an agent has limited decision support.

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

Deploy Server