Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_project_scratch_disk

Configure the project scratch disk location to control where Premiere Pro stores media cache and preview files. Use it to direct disk usage and avoid capacity issues during editing.

Instructions

Premiere Pro expanded operation: set project scratch disk.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_project_scratch_disk"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.9/5.0
Behavior2/5

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

There are no annotations, so the description is the only source of behavioral disclosure; it merely restates the operation without mentioning side effects, persistence, or dependencies. The write nature of 'set' is implied but not expanded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but the prefix 'Premiere Pro expanded operation:' adds no value and the remaining text largely repeats the tool name. It is not overly verbose, but it does not use its brevity to deliver extra insight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a setter with no annotations and no output schema, the description is too thin: it does not say what value or path will be applied, what is required before calling, or what observable change occurs. A richer sentence is needed to make this usable.

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?

Context indicates zero declared parameters, so there is little for the description to add to the schema. The permissive additionalProperties behavior is not explained, but the no-parameter baseline 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 concrete action and resource ('set project scratch disk'), so the tool's objective is clear. It does not differentiate this from sibling set_scratch_disk_path, and 'expanded operation' is filler.

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?

No guidance is provided about when to use this tool instead of related siblings such as set_scratch_disk_path or get_project_scratch_disks. No project-state or prerequisite context is given.

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