premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Select Clips In Range

select_clips_in_range

Select all clips that overlap a specified time range in the active Premiere Pro sequence, optionally filtered by track type or index.

Instructions

Select all clips that overlap a time range in the active sequence.

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": {
      "start_seconds": "<start_seconds>",
      "end_seconds": "<end_seconds>"
    },
    "name": "select_clips_in_range"
  }
}

Input Schema

Name	Required	Description
`track_type`	No	Track type (default: both)
`end_seconds`	Yes	End of selection range in seconds
`track_index`	No	Specific track index (optional)
`start_seconds`	Yes	Start of selection range in seconds
`idempotency_key`	No	Optional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
`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

B3.1/5.0

Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is partly covered, but the description adds nothing. It does not say whether the existing selection is replaced or extended, whether track_type defaults to 'both' (affecting how many clips get selected), or what happens on a sequence with no overlap — all material for a state-changing selection tool.

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?

A single well-formed sentence with the scope constraint front-loaded and no filler. It is efficiently written, though the flat single-clause form leaves no structure for the behavioral caveats a 7-parameter, nested-schema tool would benefit from.

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?

Output schema exists, so return values need no explanation, and the complex guard parameters are exhaustively described in the schema itself. Given that support, the description covers the core operation adequately; only the selection-replacement semantics and default track scope remain unstated, which is a modest gap rather than a blocking one.

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 start_seconds, end_seconds, track_type, track_index, and the guard/idempotency parameters in detail. The description does contribute one meaningful semantic: 'overlap' clarifies that partially intersecting clips are included, not just fully contained ones. That is real added value, but it is the only parameter-adjacent insight, so 3 is the correct baseline-plus.

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 gives a specific verb ('Select'), a specific resource ('all clips'), and a precise qualifier ('that overlap a time range in the active sequence'), which is enough to separate it from siblings like select_all_clips or select_clips_by_color. It stops short of naming any sibling explicitly, so the differentiation is inferable rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusivity conditions, and no mention of alternatives such as select_clips_by_name or select_clips_by_pattern. The agent must infer from the phrase 'time range' alone that this is the range-based selection tool rather than the color/name/pattern selectors.

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

Deploy Server