Skip to main content
Glama
Sign In
Adobe Premiere Pro MCP

Adobe Premiere Pro MCP

by compimprove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_zero_point

Set the zero point (timecode reference) in an Adobe Premiere Pro project to align timelines or establish a starting position for editing.

Instructions

Premiere Pro expanded operation: set zero point.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

D1.4/5.0
Behavior1/5

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

The description offers no insight into side effects, permissions, or any behavioral aspects. Since there are no annotations, this is a significant gap.

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?

The description is extremely brief, but it is front-loaded. However, it lacks enough substance to be considered appropriately sized; it is under-specified.

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?

The description is too vague to be complete. It does not place the tool in context, nor does it explain any related concepts or expected outcomes.

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?

There are no parameters to document, so the description's lack of parameter information is not penalized heavily. However, the input schema itself is unusual with propertyNames and additionalProperties but no properties, which might confuse. Still, baseline 3 given no parameters.

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

Purpose1/5

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

The description merely repeats the tool name without explaining what a 'zero point' is or what setting it accomplishes in Premiere Pro. It lacks a clear verb-resource distinction and does not differentiate from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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, why a user would set a zero point, or any prerequisites. It does not mention alternative tools.

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