premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Set Sequence In Out Points

set_sequence_in_out_points

Set a sequence's in and out points and read them back to define an export range. Out point must follow the in point and stay within sequence end.

Instructions

Set the sequence in and out points (for an export range, etc.) and read them back. out_seconds must be after in_seconds and not past the sequence end.

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": {
      "in_seconds": "<in_seconds>",
      "out_seconds": "<out_seconds>"
    },
    "name": "set_sequence_in_out_points"
  }
}

Input Schema

Name	Required	Description
`in_seconds`	Yes	In-point in seconds (0 or later)
`out_seconds`	Yes	Out-point in seconds; after in_seconds and not past the sequence end
`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

A3.5/5.0

Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds two useful behavioral facts: the call reads the points back after setting, and the range is validated against ordering and sequence end. It says nothing about what happens on out-of-range input (clamp vs. error) or about the idempotency-key and expected_cep_target guard machinery, leaving the bulk of behavioral surface to the schema.

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 tight sentences with the core action first and the validation constraint second; no filler, nothing repeated that the reader must wade through.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the read-back result need not be spelled out, but for a five-parameter mutation tool with nested reviewed-identity and idempotency guards the description is thin: it never mentions concurrency, the CEP guard, or the project-path precondition. It is adequate for the two required parameters but not for the tool's full surface.

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 ordering and end-of-sequence constraints restated in the description are already in the schema for out_seconds. The two optional, heavily nested parameters (idempotency_key, expected_cep_target) and expected_project_path are not discussed in the description at all, so it adds no meaning beyond the schema.

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 ('Set the sequence in and out points') with a concrete use case ('for an export range, etc.'), which separates it from get_sequence_in_out_points and from the item/source variants by naming the sequence. It does not explicitly name any sibling, though, so an agent must infer the boundary from the resource noun alone.

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?

The parenthetical 'for an export range, etc.' gives an implied usage context, and the constraint sentence hints at valid inputs. There is no explicit when-to-use versus set_item_in_out, set_source_in_out, or clear_sequence_in_out, and no statement of prerequisites, so guidance is only implied.

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

Deploy Server