Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

Get Project Info

get_project_info
Read-onlyIdempotent

Retrieves details about the currently open Premiere Pro project so you can inspect its structure before editing or automating timeline tasks.

Instructions

Get information about the currently open Premiere Pro project

Input Schema

NameRequiredDescriptionDefault
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.25.0
    • addedOutput schema / properties / idempotency
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Present when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.",
      +  "type": "object"
      +}
  2. Changed3 schema fields changedv1.24.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties
      Added value: +{
      +  "expected_cep_target": {
      +    "additionalProperties": false,
      +    "anyOf": [
      +      {
      +        "required": [
      +          "sequence_id"
      +        ]
      +      },
      +      {
      +        "required": [
      +          "source_item"
      +        ]
      +      }
      +    ],
      +    "description": "Optional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.",
      +    "properties": {
      +      "backend": {
      +        "const": "cep",
      +        "description": "Backend namespace for these IDs.",
      +        "type": "string"
      +      },
      +      "clip": {
      +        "additionalProperties": false,
      +        "description": "Optional exact reviewed timeline clip.",
      +        "properties": {
      +          "effect": {
      +            "additionalProperties": false,
      +            "description": "Reviewed effect and parameter identity checked before mutation.",
      +            "properties": {
      +              "display_name": {
      +                "description": "Optional exact host display name.",
      +                "maxLength": 512,
      +                "minLength": 1,
      +                "type": "string"
      +              },
      +              "match_name": {
      +                "description": "Effect match name from host inspection.",
      +                "maxLength": 512,
      +                "minLength": 1,
      +                "type": "string"
      +              },
      +              "parameter_index": {
      +                "description": "Inspected zero-based parameter index.",
      +                "maximum": 255,
      +                "minimum": 0,
      +                "type": "integer"
      +              },
      +              "parameter_name": {
      +                "description": "Exact inspected parameter name.",
      +                "maxLength": 512,
      +                "minLength": 1,
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "match_name",
      +              "parameter_index",
      +              "parameter_name"
      +            ],
      +            "type": "object"
      +          },
      +          "end_ticks": {
      +            "description": "Exact expected exclusive timeline end ticks.",
      +            "pattern": "^-?\\d{1,30}$",
      +            "type": "string"
      +          },
      +          "in_ticks": {
      +            "description": "Exact expected source In ticks.",
      +            "pattern": "^-?\\d{1,30}$",
      +            "type": "string"
      +          },
      +          "node_id": {
      +            "description": "Stable CEP node ID.",
      +            "maxLength": 512,
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "out_ticks": {
      +            "description": "Exact expected exclusive source Out ticks.",
      +            "pattern": "^-?\\d{1,30}$",
      +            "type": "string"
      +          },
      +          "project_item_id": {
      +            "description": "Expected source project-item node ID.",
      +            "maxLength": 512,
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "start_ticks": {
      +            "description": "Exact expected timeline start ticks.",
      +            "pattern": "^-?\\d{1,30}$",
      +            "type": "string"
      +          },
      +          "track_index": {
      +            "description": "Expected zero-based track index; identity still checked.",
      +            "maximum": 255,
      +            "minimum": 0,
      +            "type": "integer"
      +          },
      +          "track_type": {
      +            "description": "Expected media track group.",
      +            "enum": [
      +              "video",
      +              "audio"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "node_id",
      +          "track_type",
      +          "track_index"
      +        ],
      +        "type": "object"
      +      },
      +      "project_document_id": {
      +        "description": "Exact Premiere project document ID observed during review.",
      +        "maxLength": 512,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "sequence_id": {
      +        "description": "Stable expected active sequence ID.",
      +        "maxLength": 512,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "source_item": {
      +        "additionalProperties": false,
      +        "description": "Reviewed source identity for a source-only operation.",
      +        "properties": {
      +          "media_path": {
      +            "description": "Optional exact source-media path.",
      +            "maxLength": 4096,
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "node_id": {
      +            "description": "Exact project-item node ID.",
      +            "maxLength": 512,
      +            "minLength": 1,
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "node_id"
      +        ],
      +        "type": "object"
      +      }
      +    },
      +    "required": [
      +      "backend"
      +    ],
      +    "type": "object"
      +  },
      +  "expected_project_path": {
      +    "description": "Optional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.",
      +    "maxLength": 4096,
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / properties / receipt
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Versioned common mutation receipt; success never implies rendered verification.",
      +  "type": "object"
      +}
  3. Changed1 schema field changedv1.18.6
    • changedOutput schema / properties / data / description
      Previous value: -"Tool-specific result data when ok is true."New value: +"Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it."
  4. Changed1 schema field changedv1.14.9
    • removedInput schema / properties
      Removed value: -{}
  5. 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"
      +}
  6. Addedv1.4.0
  7. Removedv1.1.5
  8. First observedv1.1.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the "currently open" scope and omits the notable behavior disclosed in the schema: the expected_cep_target and expected_project_path fail-closed guards that make the tool refuse when the active project differs or is unsaved.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity is partly under-specification rather than compression of useful information.

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?

Output schema exists, so return values needn't be explained, and the nested guard parameters are documented in the schema. What is missing is disambiguation from the numerous other project/state readers and any mention of the refusal semantics that affect how an agent should prepare a call.

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 two optional guard parameters are already documented in detail, and the baseline of 3 applies. The description adds nothing about parameters, not even that they are optional or that omitting them preserves existing behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It states a verb and resource ("Get information about ... Premiere Pro project") with the important scope qualifier "currently open", but "information" is unspecified and the description does nothing to separate it from close siblings like get_full_project_overview, get_premiere_state, or get_project_panel_metadata. An agent cannot tell from the text what this returns that those do not.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no named alternative. With roughly 250 sibling tools including several project-level readers, the absence of any routing hint is a real gap rather than a minor omission.

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