Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set Scratch Disk Path

set_scratch_disk_path

Assigns a Premiere Pro scratch disk—captured media, previews, auto-save, CC Libraries, or motion graphics template media—to an existing folder or SameAsProject, with optional save and verification.

Instructions

Set one project scratch disk (captured media, previews, auto-save, CC Libraries or Motion Graphics template media) to an existing folder or "SameAsProject", using Premiere's ScratchDiskType constants.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path of an existing folder, or "SameAsProject"
save_and_verifyNoSave the project afterwards and confirm the saved scratch-disk settings (default: false). Premiere has no scratch-disk getter, so without this the result is unverified.
scratch_disk_typeYesWhich scratch disk to set

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.18.6
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / path / description
      Previous value: -"Full directory path for the scratch disk"New value: +"Absolute path of an existing folder, or \"SameAsProject\""
    • addedInput schema / properties / save_and_verify
      Added value: +{
+  "description": "Save the project afterwards and confirm the saved scratch-disk settings (default: false). Premiere has no scratch-disk getter, so without this the result is unverified.",
+  "type": "boolean"
+}
    • changedInput schema / properties / scratch_disk_type / description
      Previous value: -"Type: 'capturedVideo', 'capturedAudio', 'videoPreview', 'audioPreview', 'autoSave', 'ccLibraries'"New value: +"Which scratch disk to set"
    • addedInput schema / properties / scratch_disk_type / enum
      Added value: +[
+  "capturedVideo",
+  "capturedAudio",
+  "videoPreview",
+  "audioPreview",
+  "autoSave",
+  "ccLibraries",
+  "motionGraphicsTemplateMedia"
+]
    • 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."
  2. 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"
+}
  3. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  4. Addedv1.1.5
  5. Removedv1.1.5
  6. First observedv1.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare the full safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds only the constraint that the target must be an existing folder or 'SameAsProject', which the schema's path description already states; it does not disclose persistence behavior or verification needs beyond what the save_and_verify parameter documents.

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?

A single, tightly written sentence that front-loads the verb and resource, then enumerates the covered disk types with zero filler.

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?

An output schema exists, so return values need not be described, and the parameters are fully covered by the schema. The remaining gap is routing: with near-duplicate siblings ('set_project_scratch_disk', 'get_project_scratch_disks') and a mutation-adjacent tool, the description should clarify how this differs, and it does not.

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 baseline is 3. The description restates the enum categories and the 'SameAsProject' value, but adds no semantics beyond the schema (which already documents the enum, the path format, and the save_and_verify tradeoff).

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?

States a specific verb (Set) and resource (one project scratch disk) and enumerates which disk types are covered, mapping to the ScratchDiskType constants. However, it does not differentiate itself from the close sibling 'set_project_scratch_disk', which appears to address the same resource, leaving ambiguity about which tool an agent should pick.

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?

The description gives no when-to-use context, no prerequisites, and never mentions the obvious alternatives ('set_project_scratch_disk', 'get_project_scratch_disks') that exist among siblings. An agent must infer routing from name similarity alone.

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