Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Add Text Overlay

add_text_overlay

Add text overlays to Premiere Pro sequences by specifying text, start time, duration, and caption format for subtitles or title graphics.

Instructions

Unavailable: Premiere does not expose a supported scripting API to create caption clips directly from raw text. Import an .srt/.vtt and use create_caption_track, or use a MOGRT/PNG overlay for title graphics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText content to display
start_secondsNoStart time in seconds (default: 0)
caption_formatNoCaption format (default: subtitle)
duration_secondsNoDuration in seconds (default: 5)

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. Changed1 schema field changedv1.14.9
    • changedInput schema / properties / caption_format / enum
      Previous value: -[
-  "608",
-  "708",
-  "subtitle",
-  "teletext"
-]New value: +[
+  "subtitle",
+  "608",
+  "708",
+  "teletext"
+]
  2. 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"
+}
  3. Changed2 schema fields changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / caption_format / enum
      Previous value: -[
-  "subtitle",
-  "608",
-  "708",
-  "teletext"
-]New value: +[
+  "608",
+  "708",
+  "subtitle",
+  "teletext"
+]
  4. Changed3 schema fields changedv1.1.5
    • addedInput schema / properties / caption_format
      Added value: +{
+  "description": "Caption format (default: subtitle)",
+  "enum": [
+    "subtitle",
+    "608",
+    "708",
+    "teletext"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / font_size
      Removed value: -{
-  "description": "Font size (default: 60)",
-  "type": "number"
-}
    • removedInput schema / properties / track_index
      Removed value: -{
-  "description": "Video track index to place the text on (default: topmost track)",
-  "type": "number"
-}
  5. First observedv1.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that Premiere exposes no supported scripting API for this operation, making it clear the tool is a stub rather than a working mutation. This is significant behavioral context that prevents the agent from expecting a real text overlay side effect.

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 entire description is a single front-loaded sentence that states unavailability, explains why, and provides alternatives. Every phrase carries useful information with 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?

For an unavailable tool, the description is fully sufficient: it explains the limitation, names the correct alternatives, and avoids leaving the agent to guess whether the operation will work. The presence of an output schema does not require extra explanation because the tool does not execute a real operation.

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 already documents all four parameters with full coverage, so the baseline is 3. The description does not add per-parameter meaning, but given the tool is explicitly unavailable, no additional parameter detail is necessary to improve selection behavior.

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 leads with 'Unavailable' and gives a concrete reason, so an agent immediately understands this tool cannot perform its nominal action. It also names the exact alternatives (create_caption_track, MOGRT/PNG overlay), which clearly differentiates it from related captioning tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit routing guidance: import an .srt/.vtt and use create_caption_track for captions, or use a MOGRT/PNG overlay for title graphics. This tells the agent when not to call this tool and which sibling to prefer.

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