Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Select All Clips

select_all_clips

Select all clips in the active sequence, or narrow the selection to a specific video or audio track by setting track type and index.

Instructions

Select all clips in the active sequence, or all clips on a specific track.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_typeNoTrack type (default: both)
track_indexNoSpecific track index (optional, selects all tracks if omitted)

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
Behavior3/5

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

Annotations already indicate non-read-only and non-destructive behavior, so the description does not need to re-state safety. It adds useful scoping context but does not disclose whether the selection replaces or extends the current selection, which is a meaningful behavioral gap for a selection tool.

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 no filler. The primary action and both scoping modes are front-loaded, making the tool easy to parse quickly.

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 low-complexity selection tool, the description plus schema and annotations cover the essentials: what is selected, where it happens, and the optional track scoping. The only notable omission is replace-versus-extend selection behavior, which is minor here.

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 the schema already documents track_type and track_index well. The description reinforces the all-clips versus specific-track distinction but adds no new parameter-level detail beyond what the schema provides.

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?

States a specific verb and resource: 'Select all clips in the active sequence, or all clips on a specific track.' This clearly distinguishes the tool from selection-related siblings like select_clips_by_name, select_clips_in_range, and set_clip_selection by emphasizing blanket selection scope.

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

Usage Guidelines4/5

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

Clearly describes the two invocation modes: all clips in the active sequence, or all clips on a specific track. It does not explicitly name alternatives or when-not-to-use scenarios, but the scope is obvious enough to guide an agent away from more targeted selection tools.

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