premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Get Sequence Structure

get_sequence_structure

Read-onlyIdempotent

Retrieves a bounded structural page of the active Premiere Pro sequence with track counts, clips, positions, gaps, and metadata. Use it to inspect timeline state before making edits.

Instructions

Get a bounded structural page of the active sequence (50 clips by default; follow pagination.nextOffset): all track counts, paged clips with positions, gaps, and clip metadata. Essential for understanding timeline state before making edits. 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_sequence_structure"
  }
}

Input Schema

Name	Required	Description
`clip_limit`	No	Page size (default: 50, maximum: 200). Payload budget may shorten a page. Inspect nextOffset.
`track_type`	No	Track type to page (default: both). Track counts remain available.
`clip_offset`	No	Offset into matching clips (matching gaps for get_timeline_gaps), video before audio (default: 0).
`end_seconds`	No	Optional exclusive window end; must exceed start_seconds.
`sequence_id`	No	Sequence name or ID. Uses active sequence if omitted.
`track_index`	No	Optional zero-based track index within each selected type.
`start_seconds`	No	Optional inclusive window start; returns overlapping items.
`expected_cep_target`	No	Optional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
`expected_project_path`	No	Optional 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

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.
`receipt`	No	Versioned common mutation receipt; success never implies rendered verification.
`idempotency`	No	Present 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.

First observedv1.30.0Nov 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safe read-only profile, and the description adds real value beyond them: the payload is bounded (default 50, budget can shorten a page), alignment diagnostics are limited to the current page, and they explicitly 'do not verify playback sync'. That last caveat is a genuinely useful scope limit. It stops short of describing ordering or other edge behavior.

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?

Three sentences, front-loaded with the core behavior and trimmed of filler. Dense jargon ('bounded source-alignment diagnostics', 'media-pair group inconsistencies') slightly raises parsing cost but each clause carries information.

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?

An output schema exists, so return-value detail is not required. The description covers pagination, bounpary semantics, and the limits of alignment diagnostics, which is most of what an agent needs. It does not clarify how this differs from other sequence-inspection tools, which matters given the crowded sibling set.

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 all nine parameters are already documented in the schema. The description only restates a couple of details (50-clip default, following nextOffset) rather than adding semantics for clip_offset, track_index, or the expected_cep_target guard. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource plus the exact payload shape: bounded pages of the active sequence with track counts, paged clips with positions, gaps, and clip metadata. Clear about what is returned, but it never names a sibling (get_timeline_summary, get_full_sequence_info, get_timeline_gaps) to distinguish its niche.

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?

'Essential for understanding timeline state before making edits' gives a concrete usage context, and 'follow pagination.nextOffset' gives operational guidance. However, it offers no explicit when-not conditions or alternative tools for full-sequence or summary views.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server