Imports sequences from another Premiere Pro project file into the active project using a source .prproj path and sequence IDs, so you can reuse edits without rebuilding them.
Imports sequences from another Premiere Pro project file.
| Name | Required | Description | Default |
|---|---|---|---|
| projectPath | Yes | The absolute path to the source .prproj file | |
| sequenceIds | Yes | Array of sequence IDs to import from the source project |
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits, but it only states 'Imports sequences'. It does not mention whether this is a destructive action, if it overwrites existing sequences, requires the source project to be open or closed, or if it links or copies the sequences. For a mutation tool, this lack of safety or side-effect information is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence with zero wasted words. It fully fits the purpose and is front-loaded with the key verb and resource, making it efficient for an agent to quickly understand.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool (2 params, clear schema, no output schema), the description is minimal but covers the essential action. However, the lack of behavioral transparency (e.g., side effects, prerequisites) means the agent may not fully understand the consequences of invoking it, leaving the description only partially complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (both projectPath and sequenceIds have descriptions), so the baseline is 3. The description adds no extra context, such as how to obtain sequence IDs (e.g., via list_sequences) or the expected format of the project path, so it does not improve upon the schema. It is merely adequate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (imports) and the target (sequences from another project file), making its purpose unambiguous. It distinguishes itself from sibling tools like import_media or import_fcp_xml by specifying 'from another Premiere Pro project file', though it does not elaborate on the scope or side effects.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use it (when needing to bring sequences from an external .prproj file) but does not explicitly mention alternatives or when not to use it. There is a sibling tool 'import_sequences' that could be confused with this one, and no guidance is given to differentiate them, leaving the agent to infer the intended use case.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.