Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Qe Clip Info

get_qe_clip_info
Read-onlyIdempotent

Retrieve QE DOM details for a specific clip in Premiere Pro using track type, track index, and clip index to uncover properties that the standard API does not provide.

Instructions

Get QE DOM information about a clip, including properties not available through the standard API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clip_indexYesClip index on the track (0-based)
track_typeYesTrack type
track_indexYesTrack 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

A3.5/5.0
Behavior3/5

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

Annotations already signal readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile externally. The description adds only that this exposes QE DOM/non-standard data; it doesn't disclose output structure, failure modes, or operational caveats, but with the annotations and output schema present the gap is modest.

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 front-loaded sentence with no wasted words or redundant restating of the tool name or schema. The qualifier about non-standard properties earns its place by differentiating the tool.

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?

With three fully documented parameters, read-only annotations, and an output schema present, the description is minimally sufficient for making a basic call. It lacks explicit routing against sibling clip-inspection tools and a clearer definition of 'QE DOM', so an agent comparing get_qe_clip_info with get_clip_properties receives only implicit guidance.

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% and each parameter is already explained in the input schema, including 0-based indexing and the track_type enum. The description adds no additional meaning about how the parameters are used, so the schema carries the weight.

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 states a specific operation ('Get QE DOM information about a clip') and adds a distinguishing qualifier ('properties not available through the standard API') that separates it from standard clip-property tools like get_clip_properties or get_full_clip_info. However, 'QE DOM' is unexplained jargon, so an agent without domain knowledge may still be unsure exactly what is being fetched.

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 phrase 'properties not available through the standard API' implies this is for non-standard or internal DOM data rather than ordinary clip properties, but it never names alternatives or states when not to use it. Usage context is implied, not 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