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

premiere-pro-mcp

by matt-j-penny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Active Sequence

get_active_sequence
Read-onlyIdempotent

Retrieve paged details about the active Premiere Pro sequence, including clips, source In/Out times, and bounded picture/sound offset diagnostics for timeline inspection.

Instructions

Get bounded, paged information about the currently active sequence (50 clips by default). Audio and video clips include source In/Out seconds. Follow pagination.nextOffset for more. Bounded source-alignment diagnostics include separate picture/sound offsets and media-pair group inconsistencies, with limited group context outside this page; they do not verify playback sync.

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": "get_active_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_limitNoPage size (default: 50, maximum: 200). Payload budget may shorten a page. Inspect nextOffset.
track_typeNoTrack type to page (default: both). Track counts remain available.
clip_offsetNoOffset into matching clips (matching gaps for get_timeline_gaps), video before audio (default: 0).
end_secondsNoOptional exclusive window end; must exceed start_seconds.
track_indexNoOptional zero-based track index within each selected type.
start_secondsNoOptional inclusive window start; returns overlapping items.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish this as a safe read-only, idempotent operation. The description adds useful behavioral context beyond annotations: default page size, pagination via nextOffset, and the important caveat that source-alignment diagnostics are bounded and do not verify playback sync.

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?

The description is front-loaded and dense with useful information: purpose, default page size, clip metadata, pagination, and diagnostic limitations. Every sentence contributes to correct tool use without unnecessary repetition.

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?

For a read-only sequence-inspection tool with an output schema and fully described parameters, the description covers the key operational behavior and caveats. It does not detail the expected_cep_target and expected_project_path guard semantics, but those are already well covered by the schema descriptions.

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 parameter meanings are already well documented in the input schema. The description reinforces the default page size and pagination behavior but does not add substantial meaning beyond the schema for the remaining parameters, including the CEP target and project-path guards.

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 verb and resource: getting bounded, paged information about the currently active sequence. It adds meaningful scope details such as clip pagination and source-alignment diagnostics, though it does not explicitly distinguish this tool from sequence-inspection siblings like get_full_sequence_info or get_sequence_structure.

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?

Usage is implied by the active-sequence focus and the paging behavior, but there is no explicit guidance on when to choose this tool over alternatives such as get_full_sequence_info or get_timeline_summary. No when-not conditions or alternative tool names are provided.

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