Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Batch Enable Disable

batch_enable_disable

Enable or disable multiple clips at once by targeting selected clips, a specific track, or all clips in the timeline. Streamline clip state management without editing each item individually.

Instructions

Enable or disable multiple clips at once (selected, track, or all).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesWhich clips to affect
enabledYestrue to enable, false to disable
track_typeNoTrack type (required when target is 'track')
track_indexNoTrack index (required when target is 'track')

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

B3.4/5.0
Behavior2/5

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

The annotations are all false-valued (not read-only, not idempotent, not destructive) and thus carry almost no safety context, leaving the burden on the description. The description only restates the core operation and adds no detail on prerequisites (e.g., active sequence, non-empty selection), failure conditions, or effects on locked/unselected clips. For a mutating tool this is a significant behavioral gap.

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?

The description is a single front-loaded sentence with no filler — verb, resource, and scope all appear near the front. The only minor redundancy is that 'multiple clips at once' echoes the title's 'Batch' concept, but this is acceptable reinforcement rather than waste.

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?

For a 4-parameter tool with full schema coverage and an output schema present, the description conveys the core purpose adequately. It does not, however, mention the alternative singular tool, prerequisites for each target mode, or edge-case behavior (empty selection, locked tracks), which an agent would need to invoke it reliably among 180+ siblings. Adequate but with clear gaps.

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%, so all four parameters (target, enabled, track_type, track_index) are already documented, including the conditional requirement for track_type/track_index when target is 'track'. The description's parenthetical '(selected, track, or all)' merely restates the target enum and adds no new semantic meaning. Baseline 3 applies given full schema coverage.

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 ('Enable or disable'), a resource ('multiple clips'), and the targeting scope ('selected, track, or all'). The phrase 'multiple clips at once' distinguishes it from the sibling enable_disable_clip, which handles the singular case. This is immediately actionable and clearly differentiated.

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 targeting modes ('selected, track, or all') give a clear sense of when this tool applies to batch operations. However, it never names the singular sibling enable_disable_clip as the alternative for single-clip toggles, nor does it state when NOT to use it (e.g., for muting audio or locking tracks). Usage is implied rather than explicit.

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