Skip to main content
Glama

replace_mogrt_media

Replace an image in a Media Replacement slot of a timeline template clip while preserving its text, settings, effects, and keyframes. Apply to one clip or all clips using that template.

Instructions

Replace the image in a Media Replacement slot of a template clip that is already on the timeline. The clip stays in place with its text, settings, effects and keyframes. If other clips use the same template, by default only this clip changes (it is swapped for an identical copy with its settings carried over); scope 'all' changes every clip of that template in place instead.

Input Schema

NameRequiredDescriptionDefault
scopeNoclip (default) = only this clip; all = every clip using this template
clipIndexYes
trackIndexYesVideo track of the template clip
replacementsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden well: it discloses that the clip stays in place with text, settings, effects and keyframes, and explains the important copy-vs-in-place behavior for default scope versus 'all'. It does not mention failure modes, permissions, or whether the operation is reversible.

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 three focused sentences, front-loaded with the purpose and then adding preservation and scope semantics. Every sentence contributes useful information without repetition.

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

Completeness4/5

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 description provides strong behavioral context about preservation and scope. It is still missing some details an agent might want, such as error behavior and complete parameter guidance for trackIndex/clipIndex and replacements.

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 coverage is 50%, and the description meaningfully clarifies the 'scope' parameter beyond the schema by explaining the swap-for-identical-copy behavior. However, it does not explain clipIndex or fully document the replacements array structure, and it refers to 'a Media Replacement slot' singular despite the array allowing multiple replacements.

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

Purpose5/5

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

The description states a specific verb and resource: replacing the image in a Media Replacement slot of a template clip already on the timeline. The phrase 'already on the timeline' also implicitly distinguishes this from sibling tools like place_mogrt_with_media, which likely inserts new clips.

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

Usage Guidelines4/5

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

It clearly frames the usage context as a template clip already on the timeline and explains how the 'scope' parameter changes behavior. However, it does not explicitly name alternatives or state when not to use this tool versus get_mogrt_media or place_mogrt_with_media.

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