Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Capabilities

get_capabilities
Read-onlyIdempotent

Identify available Premiere Pro operations and check backend coverage, authority, and verification needs. Use keyword or exact-name search to find ranked tool matches and session availability.

Instructions

Discover Premiere operations and report backend coverage, authority, and verification requirements. Use tool_query with task keywords (for example transcript, captions, or review frames) for ranked, bounded matches available in this session. Use tool_names for exact lookups or tool_offset/tool_limit for paging. Discovery never grants authority or proves a live host is ready.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tool_limitNoMaximum tool catalog entries to return. Omit with tool_offset to preserve the complete legacy response.
tool_namesNoOptional exact tool-name allowlist. Returns only those catalog entries while retaining the overall capability summary.
tool_queryNoOptional case-insensitive keywords matched against tool names and descriptions. Exact names rank first. Search defaults to 20 results with descriptions and session availability; page with tool_offset/tool_limit.
tool_offsetNoZero-based offset into the filtered tool catalog. Pair with tool_limit for an explicitly sized page.
available_onlyNoFilter to tools registered under this session's authority and tool packs. Defaults to true for tool_query, false otherwise. Set false to diagnose unavailable matches; this does not enable them.

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. Changed13 schema fields changedv1.14.9
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / available_only
      Added value: +{
+  "description": "Filter to tools registered under this session's authority and tool packs. Defaults to true for tool_query, false otherwise. Set false to diagnose unavailable matches; this does not enable them.",
+  "type": "boolean"
+}
    • addedInput schema / properties / tool_limit / maximum
      Added value: +128
    • addedInput schema / properties / tool_limit / minimum
      Added value: +1
    • addedInput schema / properties / tool_limit / type
      Added value: +"integer"
    • addedInput schema / properties / tool_names / items / maxLength
      Added value: +256
    • addedInput schema / properties / tool_names / items / minLength
      Added value: +1
    • addedInput schema / properties / tool_names / maxItems
      Added value: +128
    • addedInput schema / properties / tool_names / minItems
      Added value: +1
    • addedInput schema / properties / tool_names / uniqueItems
      Added value: +true
    • addedInput schema / properties / tool_offset / minimum
      Added value: +0
    • addedInput schema / properties / tool_offset / type
      Added value: +"integer"
    • addedInput schema / properties / tool_query
      Added value: +{
+  "description": "Optional case-insensitive keywords matched against tool names and descriptions. Exact names rank first. Search defaults to 20 results with descriptions and session availability; page with tool_offset/tool_limit.",
+  "maxLength": 256,
+  "minLength": 1,
+  "pattern": "\\S",
+  "type": "string"
+}
  2. Changed5 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"
    • addedInput schema / properties / tool_limit
      Added value: +{
+  "description": "Maximum tool catalog entries to return. Omit with tool_offset to preserve the complete legacy response."
+}
    • addedInput schema / properties / tool_names
      Added value: +{
+  "description": "Optional exact tool-name allowlist. Returns only those catalog entries while retaining the overall capability summary.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / tool_offset
      Added value: +{
+  "description": "Zero-based offset into the filtered tool catalog. Pair with tool_limit for an explicitly sized page."
+}
    • 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. Addedv1.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Even with readOnly, idempotent, and non-destructive annotations, the description adds meaningful behavioral context: matches are ranked and bounded, availability is session-scoped, and discovery has no side effects on authority or live-host status. This goes beyond the annotations and prevents common misuse.

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?

Three dense sentences with no filler. The purpose is front-loaded, and each sentence addresses a distinct concern: what the tool reports, how to query it, and what it does not do.

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 a discovery tool with 0 required parameters, rich annotations, and an output schema, the description is complete. It covers matching, paging, session scope, authority, and the host-readiness caveat, so an agent has enough context to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents all five parameters with 100% coverage, so the baseline is 3. The description adds value by prescribing which parameter mode fits which task: keyword search via tool_query, exact lookups via tool_names, and paging via tool_offset/tool_limit, which supplements the schema.

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 action ('Discover Premiere operations') and the exact report content ('backend coverage, authority, and verification requirements'). It also distinguishes itself from sibling verification/discovery tools by clarifying that results are scoped to the current session and that discovery does not prove host readiness.

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?

It gives explicit routing guidance: use tool_query for task keywords, tool_names for exact lookups, and tool_offset/tool_limit for paging. The caveat 'Discovery never grants authority or proves a live host is ready' tells agents when not to rely on this tool, effectively differentiating it from connection-verification 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