Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Move Clip

move_clip

Reposition a clip on the timeline by specifying its node ID and new start time in seconds. Optionally set a new track to move the clip to a different track.

Instructions

Move a clip to a new position on the timeline

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYesNode ID of the clip to move
new_track_indexNoOptional new track index to move the clip to
new_start_secondsYesNew start time in seconds

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

The description only restates the basic operation and adds no behavioral context beyond the annotations, which already indicate this is a mutable, non-idempotent operation. It does not disclose whether moving a clip leaves a gap, overwrites neighboring clips, ripples the timeline, or requires any track/sequence conditions.

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?

The description is a single declarative sentence that is front-loaded and contains no filler. It is appropriately concise for a tool whose parameter details are already covered by the input schema.

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?

For a timeline mutation with many sibling editing tools, the description is too thin: it omits ripple/overwrite behavior, what happens to the clip's previous slot, and how this differs from move_clip_to_track or trim_clip. The output schema reduces the need to describe return values, but the side-effect context is still missing.

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 parameters node_id, new_start_seconds, and new_track_index are already documented. The description adds little beyond the phrase 'new position', which loosely maps to the start time and optional track parameters but does not clarify units, defaults, or behavior when new_track_index is omitted.

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 ('move'), a resource ('a clip'), and a scope ('on the timeline'), so an agent can understand the core operation. However, it does not explicitly differentiate from the sibling tool move_clip_to_track; 'new position' could refer to time, track, or both.

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

Usage Guidelines2/5

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

There is no guidance about when to use move_clip versus related timeline editing tools such as move_clip_to_track, trim_clip, set_clip_start_time, or overwrite_clip. The description provides no contextual triggers, exclusions, or alternative routing, leaving tool selection to inference.

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