Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Freeze Frame

freeze_frame

Generate a still image from a video clip at a specific timestamp, then add it to the timeline as a freeze frame.

Instructions

Create a freeze frame from a clip at a specific time. Exports the frame and imports it back as a still image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_pathYesFull path for the exported frame (e.g., /path/to/freeze.png)
time_secondsNoTime in the sequence to freeze (in seconds). Uses playhead if omitted.
duration_secondsNoDuration of the freeze frame on the timeline (default: 2)

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

A4/5.0
Behavior4/5

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

Annotations mark this as a mutating operation (readOnlyHint=false), and the description adds useful behavioral context by disclosing that the tool both exports the frame and imports it back as a still image. This reveals the side effect on the timeline beyond the schema. It does not mention file-overwrite behavior or source-clip requirements, but the core behavior is transparent.

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, tightly-written sentence that front-loads the primary action and adds the key export/import nuance without wasted words. Every segment earns its place.

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 3-parameter tool with full schema coverage and an output schema present, the description is mostly sufficient. The primary gap is that it does not specify which clip or sequence the freeze frame is created from (e.g., selected clip, playhead context), which is a relevant operational detail. Still, the essentials are covered, so only a minor gap remains.

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%, with clear descriptions for output_path, time_seconds, and duration_seconds. The description adds little beyond the schema; phrases like 'at a specific time' mirror the time_seconds parameter description. Since the schema carries the full semantic weight, a baseline score of 3 is appropriate.

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 states a specific verb-resource pair: 'Create a freeze frame from a clip at a specific time.' It further distinguishes itself from similar export/capture tools by noting the frame is 'imported back as a still image,' which sets it apart from sibling tools like export_frame or capture_frame. This makes its purpose unambiguous.

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 description implies usage: when you need to create a freeze frame from a clip. However, it does not explicitly state when to prefer this tool over alternatives (e.g., export_frame or capture_frame) nor mention prerequisites like having a clip selected or an active sequence. There is no exclusionary guidance, so an agent might struggle to choose between highly related siblings.

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