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

premiere-pro-mcp

by matt-j-penny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Timeline Gaps

get_timeline_gaps
Read-onlyIdempotent

Identify gaps between timeline clips and paginate results to locate missing content or spots where clips can be tightened.

Instructions

Find a bounded page of gaps (50 by default; follow pagination.nextOffset) on the timeline between clips. Useful for identifying where content is missing or where clips can be tightened.

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_timeline_gaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_limitNoPage size (default: 50, maximum: 200). Payload budget may shorten a page. Inspect nextOffset.
track_typeNoWhich track type to analyze (default: both)
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.
sequence_idNoSequence name or ID. Uses active sequence if omitted.
track_indexNoOptional zero-based track index within each selected type.
start_secondsNoOptional inclusive window start; returns overlapping items.
min_gap_secondsNoMinimum gap duration in seconds to report (default: 0.04 = ~1 frame at 24fps)
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.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the bar is lower. The description adds pagination behavior (default 50, follow pagination.nextOffset), which is useful, but it does not describe how gaps are computed, how track selection affects results, or other behavioral details beyond what the schema already exposes.

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?

Two compact sentences with zero waste. The core action and pagination constraint are front-loaded, followed by a brief usage-oriented rationale.

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?

Given the rich input schema, output schema, and safety annotations, the description covers the essential purpose and pagination behavior. It is nearly complete, though a brief note on how gaps relate to selected tracks or the min-gap threshold would improve agent confidence.

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 all ten parameters and nested structures. The description mentions only the default page size and pagination continuation, which adds little beyond the structured parameter documentation.

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 — find gaps on the timeline between clips — and mentions the bounded-page nature. It is clear enough to distinguish from general timeline summaries, though it does not name or explicitly contrast with siblings such as get_timeline_summary or detect_silence.

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?

It gives implied usage context (identifying missing content or places to tighten clips) but does not say when to use this tool versus alternatives, nor any exclusions or prerequisites. The guidance is useful but stops short of explicit routing.

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