Premiere Pro MCP Server

Map Source Ranges To Timeline

map_source_ranges_to_timeline

Maps source-media time ranges to their placements on a sequence track and reports source portions not present on that track. Use it to inspect where selected media appears in the timeline.

Instructions

Read-only mapping from source-media time ranges to placements on one sequence track. Reads the selected track once, maps only normal-speed forward clips, reports source portions not present on the track as unplaced, and returns bounded pages. This inspects timeline placement; it does not prove rendered or audible content.

Input Schema

Name	Required	Description
`ranges`	Yes	Source-media ranges to map; maximum 2000.
`media_path`	No	Exact media path returned by Premiere to match. Provide this or source_project_item_id.
`track_type`	Yes	Track collection to inspect.
`range_limit`	No	Maximum mapped ranges per page (default: 50, maximum: 200). Payload budget may shorten the page.
`sequence_id`	No	Sequence name or ID; uses the active sequence when omitted.
`track_index`	Yes	Zero-based index within the selected track collection.
`range_offset`	No	Zero-based offset into the input ranges after mapping (default: 0). Follow nextOffset to continue.
`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.
`source_project_item_id`	No	Project item node ID to match. Provide this or media_path.

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

B3.4/5.0

Behavior2/5

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

The description adds real behavioral substance beyond the annotations: single track read, normal-speed forward clips only, unplaced source portions reported, paged results, and an explicit disclaimer that it does not prove rendered output. However, it opens with 'Read-only mapping' while the annotations declare readOnlyHint=false, a direct signal conflict that could lead an agent to under- or over-trust the call; that conflict caps the score despite the otherwise strong disclosure.

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?

Three sentences, zero filler, and the core operation is front-loaded before the qualifiers. The closing sentence about not proving rendered/audible content earns its place by preventing a common misuse of the result.

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?

With an output schema present, return values need not be described, and the description covers the behavioral essentials an agent needs: scope, inclusion rules, unplaced reporting, and paging. The one gap is guidance on the media_path vs source_project_item_id choice and default sequence resolution, which are covered only in the schema.

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 ten parameters (paging via range_limit/range_offset, identity via media_path/source_project_item_id, the reviewed CEP guard) are already documented. The description reinforces paging ('returns bounded pages') but adds no syntax, defaults, or matching rules beyond what the schema states, 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?

The description gives a specific verb and resource ('mapping from source-media time ranges to placements on one sequence track') plus the scope (one track), which is far more precise than the title. It does not name any sibling (e.g. convert_timeline_time or map_keyframe_time_domain) to demarcate the boundary explicitly, so it lands at clear-but-undifferentiated.

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?

Applicability is only implied through constraints: 'maps only normal-speed forward clips' and 'does not prove rendered or audible content' tell the agent when the answer will be partial. There is no explicit statement of when to reach for this versus convert_timeline_time or map_keyframe_time_domain, nor of prerequisites such as an open sequence.

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

Deploy Server