Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Roll Edit

roll_edit

Roll a clip's outgoing cut by an offset, moving both timeline edges and source in/out points while verifying the edit and keeping linked audio/video in sync.

Instructions

Perform a verified roll edit at the outgoing cut of a clip using the public timeline DOM, moving both visible edges and their source in/out points and verifying all four. Linked audio/video partners get the same edit by default (include_linked); every clip is checked before any is changed. Requires readable finite media and ffprobe duration evidence for every edited source; refuses unknown duration, stills, and nonunit/reversed speed before mutation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYesNode ID of the clip
include_linkedNoAlso apply the edit to the clip's linked audio/video partners so picture and sound stay in sync (default: true).
offset_secondsYesOffset in seconds (positive = roll right, negative = roll left)

Output Schema

TableJSON 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.18.6
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / include_linked
      Added value: +{
+  "description": "Also apply the edit to the clip's linked audio/video partners so picture and sound stay in sync (default: true).",
+  "type": "boolean"
+}
    • changedOutput schema / properties / data / description
      Previous value: -"Tool-specific result data when ok is true."New value: +"Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it."
  2. Changed2 schema fields changedv1.14.4
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observedv1.1.1

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only supply the generic hint set; the description goes well beyond them with atomicity semantics ('every clip is checked before any is changed'), the verification contract ('verifying all four'), and the media preconditions and refusal cases. 'Before mutation' is consistent with readOnlyHint=false and destructiveHint=false, and the offset application is consistent with idempotentHint=false.

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 sentences, front-loaded with the operation and then the linked-partner and precondition clauses; each sentence carries distinct information. It is jargon-dense (public timeline DOM, nonunit speed) but not padded.

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

Completeness5/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. Given the high-complexity, mutation-capable nature of the tool, the description covers the essential gaps: atomicity, linked-clip behavior, precondition evidence requirements, and refusal cases.

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%, including a clear sign convention for offset_seconds and the default for include_linked, so the schema already carries the parameter burden. The description restates the include_linked default behavior but adds no format or range detail beyond it. Baseline 3 applies when the schema does the heavy lifting.

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: a roll edit performed at the outgoing cut of a clip, with both visible edges and source in/out points moved and verified. That level of detail is materially distinguishable from a generic trim. However, it never names or contrasts with the nearby siblings slide_edit and slip_edit, leaving the agent to rely on prior editorial knowledge to disambiguate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear preconditions and refusals: requires readable finite media plus ffprobe duration evidence for every edited source, and refuses unknown duration, stills, and nonunit/reversed speed before mutating. That is strong when-to-use context, but it never names an alternative tool (slide_edit, slip_edit, trim_clip) or the condition that would select one over the other.

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