Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Toggle Track Visibility

toggle_track_visibility

Show or hide a video track in Adobe Premiere Pro by setting its eye icon state with a track index and a boolean visible flag.

Instructions

Toggle a video track's visibility (eye icon)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
visibleYesTrue to show, false to hide
track_indexYesVideo track index (0-based)

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 already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the bar is lower. The description adds only the '(eye icon)' UI mapping and discloses nothing about consequences: no behavior for an invalid or audio track_index, no note that visibility is explicitly set rather than flipped, and no mention of interaction with locked tracks. No contradiction with annotations, but minimal added behavioral context.

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?

A single verb-first sentence with zero filler, which is appropriately brief for a simple 2-parameter tool. It is slightly over-terse: a few extra words clarifying that the boolean sets state explicitly rather than toggling would have resolved the central ambiguity.

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

Completeness3/5

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

Adequate for a simple tool whose schema fully documents both required parameters and whose output schema exists, so return-value explanation is not needed. The notable gaps are the unaddressed toggle-versus-set semantics and undefined behavior for non-video track indices, but nothing critical is missing for basic correct invocation.

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%: 'visible' is documented as 'True to show, false to hide' and 'track_index' as 'Video track index (0-based)'. The description itself contributes no parameter detail, so the baseline 3 applies; the schema does the necessary work.

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 names a specific verb ('Toggle') and resource ('video track's visibility') and anchors it to the UI eye icon, which helps distinguish it from siblings like mute_track (audio) and lock_track (lock state). However, the verb 'toggle' slightly misrepresents actual behavior: the required 'visible' boolean sets an explicit target state ('True to show, false to hide') rather than flipping the current state, so the semantics are a set operation, not a toggle.

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?

No guidance is given on when to use this tool versus alternatives. With closely related siblings such as mute_track, lock_track, enable_disable_clip, and batch_enable_disable, an agent gets no criteria for choosing track-level visibility over those options. The use case is only implied by the subject matter, with no exclusions or alternative routing.

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