Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set Keyframe Interpolation

set_keyframe_interpolation

Set the interpolation type (Linear, Hold, or Bezier) for a keyframe on an effect property to control how values change between keyframes.

Instructions

Set the interpolation type of a keyframe (Linear, Hold, or Bezier)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYesNode ID of the clip
effect_nameYesDisplay name of the effect
time_secondsYesTime in seconds of the keyframe
interpolationYesInterpolation type
property_nameYesDisplay name of the property

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?

Annotations are all false, providing only a minimal safety profile (a mutating operation that is not classified as read-only or destructive). The description conveys the mutation nature but does not disclose key behavioral traits: what happens if no keyframe exists at the given time, whether the prior interpolation is overwritten, or whether the operation can fail or have side effects. It also capitalizes the enum values (Linear, Hold, Bezier) differently from the schema's lowercase enum, which could mislead an agent.

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?

The description is a single efficient sentence with no filler, and the allowed values are front-loaded in the parenthetical. It earns its place, though the slight capitalization mismatch with the schema enum is a minor structural blemish.

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 mutating tool with 5 required parameters and no useful safety profile from annotations, this description is too thin. It does not mention the dependency on an existing keyframe, does not clarify the relationship to add_keyframe or set_time_interpolation, and provides no context on failure modes. The output schema covers return values, but the operational context is still incomplete.

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 fully documents all five parameters. The description adds essentially no parameter meaning beyond the schema; the parenthetical repeats the interpolation values already captured by the enum. Baseline 3 is appropriate since the schema carries 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?

The description uses a specific verb ('set') and a specific resource ('interpolation type of a keyframe'), with the parenthetical enumerating the three allowed values. It is fully clear what the tool does, and the mention of 'keyframe' implicitly distinguishes it from the sibling set_time_interpolation, but it does not explicitly draw that contrast.

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 on when to use this tool versus alternatives such as add_keyframe or set_time_interpolation. No prerequisites are stated (e.g., that a keyframe must already exist at time_seconds), no exclusions, and no alternative routing. The intended use is only weakly implied by the verb 'set'.

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