Premiere Pro MCP Server

Map Keyframe Time Domain

map_keyframe_time_domain

Read-onlyIdempotent

Translates time ticks between source, clip-relative, and sequence domains from a verified timeline snapshot, warning when outside visible range and refusing unsupported clip mappings.

Instructions

Translate source, clip-relative and sequence ticks from an inspected snapshot. Warns outside visible range; refuses nested, reverse or retimed clips until a measured mapping exists. No keyframe write or rendering claim.

Input Schema

Name	Required	Description
`domain`	Yes	Explicit time domain.
`clip_id`	Yes	Exact snapshot clip identity.
`snapshot`	Yes	Version 1 canonical snapshot from inspect_timeline_snapshot or an equivalent verified adapter; exact tick strings, host identities, completeness, tracks/clips and SHA256 revision are validated before use.
`time_ticks`	Yes	Requested time in declared domain.
`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.

Changed1 schema field changedv1.25.0Oct 24, 2026

addedOutput schema / properties / idempotency

Added value: +{
+  "additionalProperties": true,
+  "description": "Present when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.",
+  "type": "object"
+}

Addedv1.24.0Oct 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds meaningful context: it warns outside the visible range, refuses nested/reverse/retimed clips until a measured mapping exists, and disclaims keyframe writes or rendering claims. This is strong disclosure of failure modes and limitations beyond 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.

Conciseness4/5

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

Three compact sentences with the core operation front-loaded. The refusal and limitation clauses are useful rather than padding, and there is no repetition.

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 tool with a nested schema and an output schema, the description covers purpose, failure conditions, and scope limitations. It leaves return-value details to the output schema, which is appropriate, though it could explicitly connect the snapshot parameter to inspect_timeline_snapshot.

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 each parameter including the domain enum and snapshot validation. The description only echoes the three domain values and adds no extra syntax or format information, so baseline 3 is appropriate.

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 (translate) and resource (source, clip-relative and sequence ticks) and scopes it to an inspected snapshot. It is clear enough to distinguish from generic timeline conversion, though it does not explicitly name the sibling convert_timeline_time.

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 first sentence implies the tool is used when converting ticks from a snapshot, and the refusal conditions clarify when it cannot be used. However, it gives no explicit comparison to alternatives such as convert_timeline_time and does not state prerequisites for obtaining the inspected snapshot.

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

Deploy Server