Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Import Sequences

import_sequences

Import selected sequences from another Premiere Pro project into the current one by providing the source project path and sequence IDs.

Instructions

Import sequences from another Premiere Pro project file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathYesFull path to the source .prproj file
sequence_idsYesNon-empty array of sequence IDs to import from the source project.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
    • changedInput schema / properties / sequence_ids / description
      Previous value: -"Array of sequence IDs to import from the source project. If omitted, all sequences are imported."New value: +"Non-empty array of sequence IDs to import from the source project."
    • changedInput schema / required
      Previous value: -[
-  "project_path"
-]New value: +[
+  "project_path",
+  "sequence_ids"
+]
    • 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"
+}
  2. Changed2 schema fields changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / sequence_ids / items
      Added value: +{
+  "type": "string"
+}
  3. Addedv1.1.5
  4. Removedv1.1.5
  5. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the operation is expected to modify state and may not be idempotent. The description adds the key fact that this imports sequences from another Premiere Pro project file, but it doesn't clarify what happens on conflict (e.g., duplicate sequence names), whether existing sequences are overwritten, or how the response reports success/failure. With the annotations carrying the safety profile, the description provides moderate additional context but no conflict or side-effect detail.

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?

The description is a single clear sentence, front-loaded with the action and resource. It is concise and easy to parse. It could add a bit more context (like destination behavior) without becoming bloated, but as-is it is well-structured and efficient.

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?

There is an output schema (not shown in the provided context), which presumably describes the return value. The tool has only two required parameters, both documented. For a relatively simple import operation, the description plus schema covers the basics. However, it doesn't mention key contextual details: whether the source project must be closed while importing, how sequence IDs are obtained (e.g., via list_sequences on the source project), or what happens when a sequence with the same name already exists in the destination. These gaps prevent it from being fully complete.

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 both parameters (project_path and sequence_ids) are already documented in the schema. The description phrase 'from another Premiere Pro project file' reinforces the meaning of project_path. However, the description does not explain where the imported sequences land in the destination project (e.g., whether they are placed in the same bin or at root level), which is a semantic gap. Overall, the schema does the heavy lifting, and the description adds little beyond that baseline.

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 states a specific action (import) and a resource (sequences from another Premiere Pro project file), which is clear enough. However, it doesn't distinguish itself from sibling tools like import_media, import_folder, import_fcp_xml, import_ae_comps, or import_edl—all of which involve importing some asset. The verb 'import' plus 'sequences from another project file' narrows it, but explicit differentiation from those siblings is missing.

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 the tool is used when sequences need to be brought in from another .prproj file, and the parameters (project_path, sequence_ids) reinforce this. But there is no explicit statement about when to use this vs. alternatives like import_ae_comps or import_fcp_xml, nor any mention of prerequisites (e.g., the source project must be closed or the current project must be open). The usage context is implied rather than stated.

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