Skip to main content
Glama

overwrite_clip_to_timeline

Overwrite a clip onto a timeline track at a specified start time, replacing existing content in that range so edits land in the intended position.

Instructions

Add a clip to the timeline via overwrite edit (replaces existing content)

Input Schema

NameRequiredDescriptionDefault
inPointNoSource in-point in seconds
outPointNoSource out-point in seconds
startTimeYesStart time in seconds
trackTypeNoTrack type (default: video)
trackIndexYesTrack index (0-based)
projectItemIdYesThe nodeId of the project item

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

Does 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 usefully discloses the key destructive trait that this is an overwrite edit replacing existing content, but it omits permissions, reversibility, scope of replacement, and return behavior.

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

Conciseness5/5

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

The description is a single well-structured sentence that front-loads the action and method. The parenthetical efficiently adds the critical destructive behavior without unnecessary words.

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

Completeness3/5

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

With no annotations and no output schema, the description must cover operational context for a mutation tool with six parameters. It explains the overwrite behavior but does not address prerequisites, affected tracks, failure modes, or what the tool returns.

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?

Schema description coverage is 100%, so all six parameters are already documented in the schema. The description adds no parameter-level meaning beyond the general notion of adding a clip to a timeline, so the baseline score of 3 is appropriate.

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 states a specific action and resource: add a clip to the timeline via an overwrite edit. The parenthetical '(replaces existing content)' clarifies the overwrite behavior, though it does not explicitly name the sibling add_clip_to_timeline as the contrasting non-overwrite option.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: use this when the edit should overwrite existing timeline content. However, the description does not explicitly say when to use this instead of add_clip_to_timeline, nor does it mention prerequisites such as an active sequence or target track requirements.

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