Skip to main content
Glama
Sign In
premiere-pro-mcp

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set active sequence

premiere_set_active_sequence

Activates a Premiere Pro sequence by its ID, allowing you to switch the active timeline for editing.

Instructions

Open/activate a sequence by its sequenceID (from premiere_list_sequences).

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": {
      "sequenceId": "<sequenceId>"
    },
    "name": "premiere_set_active_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
sequenceIdYessequenceID of the sequence to activate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Indicates it changes active sequence, but doesn't disclose failure modes (e.g., invalid ID, external sequence) or confirm if operation is reversible. Adequate for basic understanding but lacks depth.

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?

Single clear sentence with front-loaded purpose. No extraneous words; efficient and scannable.

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?

Adequate for a simple setter with one parameter. Does not detail return value or error handling, but with no output schema, this is acceptable. Could optionally list prerequisites (e.g., sequence must exist in project).

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 coverage is 100%, so description adds only minor value by referencing premiere_list_sequences as the ID source. Baseline 3 given full schema clarity.

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?

Description clearly states the action (open/activate) and resource (sequence) with specific identifier origin (from premiere_list_sequences), distinguishing it from related tools like premiere_get_active_sequence (retrieve) and premiere_list_sequences (list).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Provides context that the sequenceID must come from premiere_list_sequences, giving clear source. Lacks explicit when-not-to-use or alternatives, but for a simple setter, this is adequate.

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