Skip to main content
Glama

remove_keyframe_range

Remove unwanted keyframes in a specified range on a Premiere Pro timeline to clean up animation and refine effect timing.

Instructions

Premiere Pro expanded operation: remove keyframe range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

C2.1/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely restates that keyframe ranges are removed, which is already implied by the tool name, and provides no information about destructiveness, prerequisites, scope, side effects, or undo behavior.

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 concise at a single sentence, but the phrase 'Premiere Pro expanded operation' adds no value and the rest essentially repeats the tool name. It is brief but not meaningfully informative.

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?

With no annotations, no output schema, no parameters, and no relationship to sibling keyframe tools, the description leaves an agent without critical context. It fails to explain what state is required, what 'range' refers to, or what the tool actually operates on.

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 input schema is empty with zero parameters, so there is nothing for the description to add. The baseline for zero-parameter tools is 4, and no parameter information is missing.

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: remove keyframe range' is effectively the tool name in sentence form. It states a verb and resource but does not clarify what a keyframe range is, which property or sequence it applies to, or how it differs from similar tools like remove_keyframe.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention remove_keyframe, get_keyframes, or any condition such as requiring a selected clip or a defined time range. An agent cannot determine the appropriate context for this tool.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tro2789/scout-premiere-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server