Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

overwrite_from_source

Replaces a clip on the timeline with content from a specified source, enabling overwrite editing in Adobe Premiere Pro.

Instructions

Premiere Pro expanded operation: overwrite from source.

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": "overwrite_from_source"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2/5.0
Behavior1/5

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

With no annotations available, the description carries the full burden of disclosing behavior. It offers no information about side effects, whether the operation is destructive, what 'overwrite' entails, or what happens to the source and timeline. The vague phrase 'expanded operation' adds no useful context.

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

Conciseness2/5

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

While the description is extremely short, this is under-specification rather than effective conciseness. Similar to the 'Process' calibration example, the description fails to convey any meaningful information and wastes the opportunity to clarify the operation.

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

Completeness1/5

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

For a tool with no annotations, no output schema, and no parameters, the description must fully explain the operation's effect and context. It fails to do so, leaving the agent without essential information about what 'overwrite from source' does, what inputs it implicitly uses, or what the expected outcome is.

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?

The tool has 0 parameters, and the rubric sets a baseline of 4 for this case. There are no parameter descriptions needed, and the schema trivially covers all parameters. The description adds no parameter info, but it's not required.

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

Purpose2/5

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

The description 'Premiere Pro expanded operation: overwrite from source' essentially restates the tool name without explaining what 'overwrite from source' means. It lacks a specific verb+resource structure and does not distinguish itself from siblings like 'insert_from_source' or 'overwrite_clip', leaving the purpose vague.

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 on when to use this tool versus alternatives such as 'insert_from_source' or 'set_source_in_out'. The description gives no context on prerequisites, use cases, or exclusions, so the agent is left without any usage direction.

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