premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Get Full Sequence Info

get_full_sequence_info

Read-onlyIdempotent

Retrieve bounded Premiere Pro sequence details—settings, tracks, clips, markers, transitions, in/out points, and work area—with pagination for large timelines.

Instructions

Get bounded information about a sequence (50 clips by default; follow pagination.nextOffset; markers and transitions capped at 50 per collection): settings, all tracks with lock/mute/target state, paged clips with positions/effects/speed/enabled state, bounded markers, transitions, in/out points, and work area. 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_full_sequence_info"
  }
}

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.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds real behavior detail: payload budget may shorten pages, per-collection caps at 50, and that source-alignment diagnostics give only limited group context and do not verify playback sync. That last caveat is valuable beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core paging constraint is front-loaded, which is good, but the first sentence is a long run-on with a parenthetical and a dense clause list that is hard to parse in one pass. Every element is relevant, but the structure could be split for readability.

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 9-parameter read tool with a full output schema and rich annotations, the description covers scope, paging behavior, and the important limitation of the alignment diagnostics. Return-value formatting need not be explained because the output schema exists; only sibling routing guidance is missing.

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 the schema already documents clip_limit, track_type, offsets, and the window parameters. The description restates the default of 50 and the nextOffset paging model but adds no new syntax or semantics beyond the schema, so baseline 3 applies.

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 ("Get bounded information about a sequence") and enumerates the payload contents (settings, tracks, clips, markers, transitions, in/out points, work area). It is distinguishable from narrower siblings like get_sequence_settings or get_sequence_structure by breadth, though it never names those alternatives explicitly.

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?

Implies the tool is for comprehensive sequence inspection and gives operational guidance (50 clips by default, follow pagination.nextOffset, caps on markers/transitions). It does not say when to prefer get_sequence_structure, get_timeline_summary, or get_full_clip_info instead, leaving the choice to inference.

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

Deploy Server