Skip to main content
Glama
Sign In
Adobe Premiere Pro MCP

Adobe Premiere Pro MCP

by compimprove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_sequence_from_clips

Build a new Premiere Pro sequence directly from selected clips, organizing them into a timeline for immediate editing.

Instructions

Premiere Pro expanded operation: create sequence from clips.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_sequence_from_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior, but it only states the action. It doesn't reveal what 'expanded' means, whether it modifies existing clips, requires a selection, or has side effects. The operational implications are entirely undisclosed.

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, front-loaded sentence with no filler. It is concise and easy to parse, though it could benefit from a few clarifying details without becoming verbose.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of creating a sequence from clips (selection, arrangement, settings), the description is far too minimal. It does not explain what inputs are expected, how clips are chosen, or what the resulting sequence looks like. No annotations or output schema compensate for this gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since there are zero parameters, the schema fully covers parameter semantics (there are none). The description doesn't need to add parameter details, so the baseline of 4 applies. It adds no unnecessary info but provides a basic scaffold.

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 'Premiere Pro expanded operation: create sequence from clips' clearly states the primary action (create sequence from clips). It uses a specific verb and resource, but the vague 'expanded operation' phrase and lack of distinction from sibling tools like 'create_sequence' and 'create_sequence_from_preset' prevent 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 Guidelines2/5

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

The description provides no guidance on when to use this tool instead of alternatives. It doesn't mention prerequisites, context (e.g., needing selected clips), or exclusions, despite the wide range of sibling creation 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