premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Set Clip Start Time

set_clip_start_time

Sets and verifies a project item's source start timecode offset in seconds, letting you correct clip timing before editing. Use it when a clip's start time needs adjustment.

Instructions

Alias of set_start_time: set and verify the source project item start timecode offset.

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": {
      "item_id": "<item_id>",
      "start_seconds": "<start_seconds>"
    },
    "name": "set_clip_start_time"
  }
}

Input Schema

Name	Required	Description
`item_id`	Yes	Node ID or name of the project item, or the sequence ID of a sequence
`start_seconds`	Yes	New start time 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 already declare this is not read-only, not destructive, and not idempotent. The only added behavior is the word 'verify' (a readback of the new offset), with no disclosure of what verification covers, what happens when verification fails, whether the change is rolled back, or how the CEP guard and idempotency key affect the mutation. For a write operation with a nested pre-flight guard schema, that is thin.

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 front-loaded sentence with no filler and no repetition of the title. Its brevity is efficient, though it borders on under-specification rather than crisp summarization.

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

Completeness2/5

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

The tool carries five parameters including a nested expected-state guard and an idempotency key, plus an output schema, yet the description explains none of the alias semantics or what 'verify' returns. An agent cannot tell from this text how the alias differs operationally from set_start_time.

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% and every parameter, including idempotency_key and expected_cep_target, is documented in the schema. The description adds no meaning about item_id resolving a sequence versus a project item, or about start_seconds semantics on source timecode, 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 concrete verb pair ('set and verify') and a concrete resource ('source project item start timecode offset'), and explicitly names the sibling it aliases (set_start_time). That is clearer than bare 'set start time', though the alias relationship means the agent still must know set_start_time to understand scope.

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?

Saying it is an alias of set_start_time implies the two are interchangeable, but it gives no when-to-use guidance: nothing says whether to prefer this name, whether both exist for compatibility, or what conditions distinguish it from set_start_time or set_clip_duration.

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

Deploy Server