Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_sequence

Creates a new Premiere Pro sequence from an installed .sqpreset file without opening the New Sequence dialog, so preset-based edits start directly from a specified sequence preset.

Instructions

Creates a new sequence from a specific installed .sqpreset file without opening Premiere's New Sequence dialog. For footage-driven edits, prefer create_sequence_from_clips; for an empty copy of an existing sequence, use duplicate_sequence with clearContents=true.

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": {
      "name": "<name>",
      "presetPath": "<presetPath>"
    },
    "name": "create_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name for the new sequence
presetPathYesAbsolute path to an installed Premiere .sqpreset sequence preset. Required so Premiere does not show the native New Sequence dialog.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are present, so the description must disclose behavioral traits. It discloses that it bypasses the dialog and requires an installed preset. It could additionally mention that it creates the sequence in the current project, but this is reasonably implied. The disclosure is adequate but not exhaustive.

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 concise sentences, front-loaded with the core function, then alternatives. Every word earns its place; no redundancy.

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?

The description is complete for its purpose: it explains what it does, avoids a dialog, and points to alternatives. No output schema exists, but that's typical for a creation tool. It might have mentioned the sequence is added to the current project, but this is implied and not critical.

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?

The input schema provides 100% coverage for both parameters, including a detailed description for presetPath (explaining it avoids the dialog). The tool description repeats this information without adding new semantic detail, so it adds no value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it creates a new sequence from a .sqpreset file without opening the New Sequence dialog. Distinguishes from sibling tools create_sequence_from_clips and duplicate_sequence, making the unique purpose explicit.

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?

Directly advises when to use alternatives: for footage-driven edits prefer create_sequence_from_clips, and for an empty copy use duplicate_sequence with clearContents=true. This provides clear when/when-not guidance.

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