Skip to main content
Glama

Consolidate And Transfer

consolidate_and_transfer

Collects or transcodes project media and sequences into a new destination project via Premiere's Project Manager. Use it to archive a project with all its media and confirm the copied project folder exists.

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.

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": {
      "destination_path": "<destination_path>"
    },
    "name": "consolidate_and_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
transcodeNoTranscode media to match the sequence instead of copying it (default: false)
rename_mediaNoRename media to match clip names (default: false)
exclude_unusedNoExclude unused clips (default: true)
idempotency_keyNoOptional 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.
convert_ae_compsNoConvert After Effects compositions (default: false)
destination_pathYesDestination folder path for the consolidated project
convert_syntheticNoConvert synthetic importer items (default: false)
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
copy_to_new_locationNoMust be true (the default): Premiere's scripted Project Manager always collects media into the destination.
expected_project_pathNoOptional 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.
include_all_sequencesNoInclude all sequences (default: true). If false, only active sequence is used.
include_preview_filesNoInclude preview/render files (default: false)
convert_image_sequencesNoConvert image sequences to clips (default: false)

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent 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.

  1. First observedv1.30.0

TDQS

A3.7/5.0
Behavior4/5

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

With annotations only saying readOnlyHint=false and destructiveHint=false, the description adds genuinely useful behavior: it writes a Copied_<project> folder, creates the destination if missing, and only reports success once the folder contains the copied .prproj with files listed. That discloses the filesystem side effect and the success criterion, which the annotations do not. It does not cover failure modes or what happens to pre-existing content in the destination.

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, front-loaded with what the tool does and followed by the concrete on-disk contract and success condition. No filler, no restatement of the title, and the folder-naming detail is placed where it is most needed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 explained, and the schema covers all parameters. However, for a 13-parameter mutation with a nested CEP guard and a required copy_to_new_location=true constraint, the description omits any mention of the guard parameters, the mandatory flag, or what a partial failure looks like.

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 the schema already documents all 13 parameters including the idempotency key and CEP identity guard. The description adds meaning for destination_path (folder created if missing, Copied_<project> subfolder written inside it) and notes copy versus transcode behavior. This is a modest addition over an already self-documenting schema, so baseline 3 is appropriate.

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 pair (collect/copy or transcode) applied to a specific resource (project media) and names the mechanism (Premiere's Project Manager). An agent can tell this is the media-consolidation tool rather than a duplicate-finder, though it never explicitly contrasts itself with the similarly named consolidate_duplicates sibling.

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 description frames the operation as moving media into 'a new project,' which hints at the archival/transfer scenario, but it gives no explicit when-to-use, when-not-to-use, or alternative tool routing. The agent must infer that this is the heavy media-copy operation versus simpler export tools.

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

Deploy Server

Other Tools