Premiere Pro MCP Server

Get Advanced Feature Support

get_advanced_feature_support

Read-onlyIdempotent

Determine if Premiere Pro collaboration and AI features are available: checks backend, entitlements, network access, and version. Reports prerequisites and user-assisted boundaries for eligibility.

Instructions

Report public-API support, prerequisites, entitlements, and user-assisted boundaries for Premiere collaboration and AI features

Input Schema

TableJSON Schema

Name	Required	Description
`backend`	No	Backend being evaluated (default: cep, the current production MCP transport)
`frameio_entitled`	No	Whether the operator has confirmed Frame.io account/project access
`premiere_version`	No	Optional Premiere version such as 26.3.0 for version-specific eligibility
`network_available`	No	Whether required Adobe/cloud services are reachable
`generative_ai_entitled`	No	Whether the operator has confirmed Adobe generative AI entitlement

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.14.4Aug 29, 2026

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"
+}

Addedv1.4.0Jul 27, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that this reports 'user-assisted boundaries,' which hints at interactive/assisted workflows but does not explain what that means in practice. No contradiction with annotations.

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, focused sentence that front-loads the primary action ('Report') and the key subject matter. It is efficiently worded, though the phrase 'user-assisted boundaries' is somewhat of a jargon-heavy noun pile that could be clearer.

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?

The presence of an output schema reduces the need to explain return values, and the optional parameters are all individually described. However, with closely related siblings like get_av_feature_support and get_capabilities, the description would be more complete if it clarified when this specific advanced feature check is the right choice.

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 input schema fully documents all five optional parameters, including the backend enum and boolean entitlement flags. The description adds no parameter-level detail, but it does not need to because the schema already carries that burden.

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 uses a specific verb ('Report') and names the resource: public-API support, prerequisites, entitlements, and user-assisted boundaries for Premiere collaboration and AI features. It is clear enough to distinguish from the general get_capabilities tool, though it does not explicitly contrast with the similarly named get_av_feature_support sibling.

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 description implies this tool is for checking support/entitlements before using collaboration or AI features, but it never states when to prefer it over get_av_feature_support or get_capabilities. No explicit usage context, prerequisites, or exclusions are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server