Inserts a freeze frame at a chosen time within a clip, holding that frame for a set duration to emphasize a moment.
Apply a freeze frame (hold frame) at a specific point in a clip
| Name | Required | Description | Default |
|---|---|---|---|
| time | Yes | Time in seconds (relative to clip start) to freeze at | |
| duration | Yes | Duration of the freeze frame in seconds | |
| clipIndex | Yes | Clip index | |
| trackType | Yes | Track type | |
| trackIndex | Yes | Track index |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It indicates a mutation ('apply') but does not explain whether the freeze frame extends clip duration, affects linked audio, is reversible, or what happens to existing clip content after the freeze point.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no wasted words. It communicates the core action and location efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations and no output schema, the definition is incomplete. It does not cover behavioral effects on the timeline, required permissions or selection state, or what the tool returns or changes.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all five parameters are already documented in the schema. The description reinforces that the freeze applies at a specific point in a clip, but adds no parameter-level detail beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: apply a freeze frame at a specific point in a clip. It is clear what the tool does, though it does not explicitly differentiate itself from nearby timeline-editing siblings such as razor_clip or add_adjustment_layer.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as clip selection or applicable track types. Usage is only implied by the phrase 'at a specific point in a clip'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.