Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Context Edit Plan

create_context_edit_plan
Read-onlyIdempotent

Generate a non-mutating edit plan from indexed Premiere Pro context, ranking source/time candidates and flagging stale state for review before any timeline changes.

Instructions

Create a non-mutating, evidence-backed edit-plan scaffold from indexed Premiere context. It returns ranked source/time candidates and stale-state guards; the model must review them and use preview_edit_plan before any mutation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentYesEditing goal, such as finding the strongest budget explanation for a rough cut
strategyNoPlanning mode; default rough_cut
project_idYesProject context ID returned by manage_project_context capture
sequence_idNoOptional exact sequence ID filter
max_candidatesNoMaximum 25; default 8

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. Addedv1.11.3

TDQS

A4.5/5.0
Behavior5/5

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

The description goes beyond the annotations by stating non-mutating behavior, describing the return value as ranked candidates and stale-state guards, and requiring model review before any subsequent mutation. This gives the agent a clear behavioral contract without contradicting readOnlyHint or idempotentHint.

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?

Two dense, purposeful sentences front-load the tool's core nature and immediately state the workflow constraint. No filler or redundant restatement of the schema or title.

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?

Combined with a rich schema, an output schema, and safety annotations, the description supplies the essential behavioral context and next-step workflow. The mention of indexed context, ranked candidates, stale-state guards, and the preview_edit_plan prerequisite is enough for correct invocation.

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?

The input schema provides 100% coverage with meaningful descriptions for all five parameters, so the description does not need to restate them. It adds no parameter-specific detail beyond the general notion of ranked source/time candidates, so the schema carries the semantic weight.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific verb and resource ('Create ... edit-plan scaffold') and characterizes the output as ranked source/time candidates plus stale-state guards. It clearly distinguishes this non-mutating planning tool from mutation-oriented siblings by explicitly requiring preview_edit_plan before any mutation.

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?

It states when to use the tool — building an evidence-backed plan from indexed Premiere context — and explicitly routes the model to preview_edit_plan before mutation. However, it does not contrast with create_editorial_plan or spell out cases where this tool should be skipped.

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