premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Set Keyframe Interpolation

set_keyframe_interpolation

Set an existing keyframe's interpolation to Linear, Hold, or Bezier to control how a property transitions between values. Verify the write with a test export, since Premiere cannot report it back.

Instructions

Set the interpolation type of an existing keyframe (Linear, Hold, or Bezier). Premiere exposes no interpolation readback, so a write is reported as committed_unverified. Stored curves do not establish rendering; verify with a short video export, or with PNG stills composited over black (they carry straight alpha).

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": {
      "node_id": "<node_id>",
      "effect_name": "<effect_name>",
      "property_name": "<property_name>",
      "time_seconds": "<time_seconds>",
      "interpolation": "<interpolation>"
    },
    "name": "set_keyframe_interpolation"
  }
}

Input Schema

Name	Required	Description
`node_id`	Yes	Node ID of the clip
`effect_name`	Yes	Display name of the effect
`time_seconds`	Yes	Seconds from the clip's start on the timeline (0 is the clip's first frame) of the keyframe
`interpolation`	Yes	Interpolation type
`property_name`	Yes	Display name of the property
`property_index`	No	Optional property index from get_effect_properties; required when property_name is duplicated.
`idempotency_key`	No	Optional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
`expected_cep_target`	No	Optional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
`expected_project_path`	No	Optional 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

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.
`receipt`	No	Versioned common mutation receipt; success never implies rendered verification.
`idempotency`	No	Present 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.

First observedv1.30.0Nov 14, 2026

TDQS

A4.1/5.0

Behavior5/5

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

This goes well beyond the annotations by disclosing that Premiere exposes no interpolation readback, so writes are reported as committed_unverified rather than confirmed. It also warns that stored curves do not establish rendering and names two concrete verification paths (short export, or PNG stills over black carrying straight alpha) – exactly the kind of hidden behavior an agent cannot get from readOnlyHint/destructiveHint.

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?

Three sentences, each earning its place: what it does, how the result is reported, how to verify it. The core action is front-loaded and there is no filler.

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?

With a rich input schema, an output schema, and existing annotations, the description fills the one gap structured fields cannot: that success is unverified and how to confirm the visual result. Nothing an agent needs to call this correctly appears 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 coverage is 100% and the schema is extremely detailed, so the baseline is 3. The description only reinforces the interpolation enum values and the 'existing keyframe' precondition, adding no new meaning for node_id, effect_name, property_name, or the idempotency and expected-target parameters.

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: 'Set the interpolation type of an existing keyframe', and enumerates the three supported modes (Linear, Hold, Bezier). It does not explicitly disambiguate from the sibling set_time_interpolation, so an agent must infer the split between value interpolation and time interpolation.

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?

'Existing keyframe' implies the keyframe must already exist and that add_keyframe precedes this call, and the verification advice gives post-call guidance. However, there is no explicit statement of when to prefer this over set_time_interpolation or what to do on failure besides exporting a check video.

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

Deploy Server