Skip to main content
Glama
Sign In
premiere-pro-mcp

premiere-pro-mcp

by matt-j-penny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Convert Timeline Time

convert_timeline_time
Read-onlyIdempotent

Convert exact Premiere timeline values between ticks, frames, samples, seconds, and timecode using rational frame rates and selectable rounding, including drop-frame.

Instructions

Convert exact Premiere tick strings, rational frames, samples, decimal seconds and signed/drop-frame timecode locally. Nearest ties round away from zero; intervals use inclusive start and exclusive end. No floating-point tick parsing or host dispatch.

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": {
      "value": "<value>",
      "from": "<from>",
      "to": "<to>",
      "frame_rate": "<frame_rate>"
    },
    "name": "convert_timeline_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesOutput unit.
fromYesInput unit.
valueYesExact decimal ticks/frame/sample/seconds or timecode string.
roundingNoRounding policy; default nearest.
drop_frameNoUse semicolon drop-frame timecode at30000/1001 or60000/1001.
frame_rateYesExact rational frames per second; e.g. 30000/1001.
sample_rateNoRequired for sample input.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional 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

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent 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.

  1. First observedv1.30.0

TDQS

A3.7/5.0
Behavior4/5

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

With annotations already declaring readOnly/idempotent/non-destructive, the description adds real behavioral detail beyond the structured fields: tie-breaking ('nearest ties round away from zero'), interval conventions ('inclusive start and exclusive end'), and the no-floating-point-tick-parsing guarantee. It could still say what happens on out-of-range or mismatched frame rates, so not a 5.

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?

Two dense but efficient sentences; the core action and unit list are front-loaded and every clause carries information (rounding, interval bounds, locality). Slightly list-heavy but no wasted phrasing.

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?

An output schema exists, so return values need not be explained, and the schema covers the 9 parameters in depth. The description supplies the non-obvious semantic rules an agent could not infer, so it is complete enough, with only minor gaps around error behavior.

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 every parameter, including rounding, drop_frame, sample_rate, and the expected_* guards. The description mostly restates the unit enums and adds only the rounding/interval semantics, which is the baseline-3 case for high schema coverage.

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 states a specific verb+resource (convert time values) and enumerates the supported unit space (ticks, rational frames, samples, decimal seconds, signed/drop-frame timecode), which makes it clearly distinct from the timeline-editing siblings. It does not explicitly name an alternative tool, so it stops short of the top score.

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 phrase 'locally' and 'no host dispatch' implies this is a pure computation tool that needs no Premiere connection, which is useful routing signal. However, it never says when to prefer this over in-tool parameters like in_ticks/out_ticks on the mutation tools, nor any prerequisites. Usage is implied rather than stated.

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

Deploy Server

Other Tools