Premiere Pro MCP Server

Get Full Project Overview

get_full_project_overview

Read-onlyIdempotent

Retrieve a complete Premiere Pro project overview with statistics, sequences, and bin tree. For large projects, disable the bin tree or set sequence limits.

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.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

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.9/5.0

Behavior4/5

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

The annotations already establish readOnly, idempotent, nondestructive behavior. The description adds useful behavioral context beyond annotations by warning that the response can be large and recommending bounded parameters for large projects, which helps an agent anticipate heavy payloads.

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?

Two sentences with no filler: the first states the tool's purpose, and the second gives immediately actionable parameter guidance. The most important behavioral caveat is front-loaded and clearly worded.

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 read-only overview tool with no required parameters, an output schema, and safety annotations, the description is nearly complete. It could have briefly enumerated what the overview includes, but the combination of the purpose statement, parameter guidance, and output schema covers the essential context an agent needs.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds value by explaining the practical intent behind include_bin_tree, sequence_offset, and sequence_limit as a way to bound response size on large projects, going beyond raw parameter definitions.

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 clearly states the tool gets a comprehensive overview of the project, with a specific verb and resource. It does not explicitly differentiate itself from similar siblings like get_project_info, but the 'comprehensive overview' phrasing and the bin-tree/sequence parameters make the scope reasonably distinct.

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 offers conditional usage guidance: use include_bin_tree false or sequence_offset/sequence_limit for a bounded response on large projects. However, it does not say when to prefer this tool over alternatives or when a different tool like get_project_info would be more appropriate.

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

Deploy Server