Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Relink Media

relink_media

Changes a media item's file path in Premiere Pro via the legacy CEP route; disabled by default because it can block Premiere, so use only when the UXP option is unavailable.

Instructions

Legacy CEP relink can block Premiere indefinitely, even for an existing file on Premiere 26.5.2. Prefer relink_offline_media_uxp, which checks capability and reads the result back. This CEP route refuses by default; allow_unsafe_cep_relink must be explicitly true to attempt it, and its result is never reported as verified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesNode ID or name of the item to relink
new_pathYesNew file path for the media
allow_unsafe_cep_relinkNoExplicitly permit the legacy CEP changeMediaPath call. It can wedge Premiere even when the target file exists; prefer relink_offline_media_uxp.

Output Schema

TableJSON 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.19.0
    • addedInput schema / properties / allow_unsafe_cep_relink
      Added value: +{
+  "description": "Explicitly permit the legacy CEP changeMediaPath call. It can wedge Premiere even when the target file exists; prefer relink_offline_media_uxp.",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv1.18.6
    • addedInput schema / additionalProperties
      Added value: +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."
  3. Changed2 schema fields changedv1.14.4
    • 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"
+}
  4. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  5. Addedv1.1.5
  6. Removedv1.1.5
  7. First observedv1.1.1

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the operational hazard (can block/wedge Premiere indefinitely, even for an existing file on 26.5.2), the fail-safe default (refuses unless opted in) and the trust limitation (result is never reported as verified). Annotations only say readOnly=false, destructive=false, idempotent=false; the description supplies the real risk profile.

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?

Three front-loaded sentences ordered as hazard, recommended alternative, then default behavior and caveat; no filler. Slightly dense in the opening clause but every sentence earns its place.

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

Completeness5/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-value explanation is unnecessary. The description supplies the safety posture, default refusal, override flag and the verification gap, which is everything an agent needs to call this hazardous legacy route correctly.

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 description coverage is 100%, so item_id, new_path and allow_unsafe_cep_relink are already documented in the schema. The description reinforces the semantics of the safety flag (must be explicitly true, default refusal), but adds no syntax or format detail beyond what the schema already carries.

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 identifies the operation as the legacy CEP relink route and immediately contrasts it with the preferred relink_offline_media_uxp, so an agent can separate the two without opening a schema. The core verb/resource is implicit ('Legacy CEP relink...') rather than stated in a leading 'Relinks item_id to new_path' clause, which is the only thing keeping it from 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 Guidelines5/5

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

Explicit when-not guidance: prefer relink_offline_media_uxp because it checks capability and reads the result back. It further states this route refuses by default and only proceeds when allow_unsafe_cep_relink is explicitly true, giving a clear conditional path for both the normal and override cases.

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