Premiere Pro MCP Server

Get Full Project Overview

get_full_project_overview

Read-onlyIdempotent

Retrieve a complete view of an Adobe Premiere Pro project, including statistics, sequences, and optional bin tree. Control bin depth or sequence range to keep large-project responses manageable.

Instructions

Get a comprehensive overview of the project. Use include_bin_tree false or sequence_offset/sequence_limit for a bounded response on large projects.

Input Schema

TableJSON Schema

Name	Required	Description
`max_bin_depth`	No	Maximum recursive bin-tree depth when include_bin_tree is true (default: 10).
`sequence_limit`	No	Maximum sequences to include. Omit to preserve the complete legacy response.
`sequence_offset`	No	Zero-based offset into project sequences.
`include_bin_tree`	No	Include the recursive bin tree (default: true). Set false to return project statistics and sequences only.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.18.6Sep 30, 2026

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."

Changed9 schema fields changedv1.14.9Sep 8, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / max_bin_depth / maximum
```
Added value: +10
```
- addedInput schema / properties / max_bin_depth / minimum
```
Added value: +0
```
- addedInput schema / properties / max_bin_depth / type
```
Added value: +"integer"
```
- addedInput schema / properties / sequence_limit / maximum
```
Added value: +500
```
- addedInput schema / properties / sequence_limit / minimum
```
Added value: +1
```
- addedInput schema / properties / sequence_limit / type
```
Added value: +"integer"
```
- addedInput schema / properties / sequence_offset / minimum
```
Added value: +0
```
- addedInput schema / properties / sequence_offset / type
```
Added value: +"integer"
```

Changed6 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"

addedInput schema / properties / include_bin_tree

Added value: +{
+  "description": "Include the recursive bin tree (default: true). Set false to return project statistics and sequences only.",
+  "type": "boolean"
+}

addedInput schema / properties / max_bin_depth

Added value: +{
+  "description": "Maximum recursive bin-tree depth when include_bin_tree is true (default: 10)."
+}

addedInput schema / properties / sequence_limit

Added value: +{
+  "description": "Maximum sequences to include. Omit to preserve the complete legacy response."
+}

addedInput schema / properties / sequence_offset

Added value: +{
+  "description": "Zero-based offset into project sequences."
+}

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

First observedv1.1.1May 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered; the description adds genuinely new behavioral context by warning that the default response can be large and how to bound it. It stops short of describing the response shape, but an output schema exists to carry that.

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?

Two short sentences with no filler, and the core purpose is front-loaded ahead of the mitigation advice. It is appropriately sized, though the second sentence compresses three parameters into one clause rather than fully explaining their interplay.

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 zero-required-parameter, read-only overview tool with a full output schema and complete parameter descriptions, the description covers purpose and the main operational caveat. The only meaningful gap is lack of differentiation from adjacent project-info siblings.

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 each parameter already documents itself including defaults and ranges. The description only echoes include_bin_tree, sequence_offset and sequence_limit by name without adding format or interaction detail beyond the schema, so the baseline of 3 applies.

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 names a specific verb ('Get') and resource ('overview of the project') with a scope qualifier ('comprehensive'), so the agent knows what is returned. It does not, however, distinguish this from closely related siblings such as get_project_info or get_full_sequence_info, which the agent must resolve on its own.

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?

It gives one concrete usage rule — use include_bin_tree false or sequence_offset/sequence_limit for a bounded response on large projects — which is real conditional guidance. It says nothing about when to prefer this over other project-level inspection tools, so the when-to-use-vs-alternative dimension is only implied.

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

Deploy Server