Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set Override Frame Rate

set_override_frame_rate

Override a project item's frame rate to correct misinterpreted media or image sequences. Specify item and desired frame rate to fix playback timing.

Instructions

Override the frame rate of a project item (useful for image sequences or misinterpreted media)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesNode ID or name of the project item
frame_rateYesFrame rate to set (e.g., 23.976, 24, 29.97, 30, 60)

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. Addedv1.1.5
  4. Removedv1.1.5
  5. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already signal mutation (readOnlyHint=false), and the description's 'Override' verb is consistent with that, so there is no contradiction. The description adds minor behavioral context — the override applies at the project-item level and addresses mis-interpreted media. However, it doesn't disclose whether calling it again replaces the existing override, whether the override can be reset to the native rate, or what side effects occur on sequences referencing the item.

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?

A single sentence with the action front-loaded and a compact parenthetical use case. Every word earns its place; there is no filler or redundancy.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 2-parameter setter with fully documented schema and an output schema present, the description is largely complete. The only meaningful gap is the absence of guidance on how to revert an override back to the native frame rate, which an agent might need when correcting a mistake. This is minor given the tool's simplicity.

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%: item_id is documented as 'Node ID or name of the project item' and frame_rate includes example values (23.976, 24, 29.97, 30, 60). The description adds the purpose context but no additional parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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 and resource ('Override the frame rate of a project item') and adds a concrete use case ('useful for image sequences or misinterpreted media'). The 'project item' scope implicitly distinguishes it from set_sequence_frame_rate, which targets sequences. However, it doesn't explicitly differentiate itself from closely related setters like set_override_pixel_aspect_ratio or set_footage_interpretation, leaving some differentiation to inference.

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?

The parenthetical 'useful for image sequences or misinterpreted media' implies the intended scenario: correcting items whose detected frame rate is wrong. But it doesn't name alternatives (e.g., set_footage_interpretation, set_sequence_frame_rate) or state when NOT to use this tool, so an agent must infer the boundary from the sibling list rather than from explicit guidance.

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