Change a Motion Graphics template property in Premiere Pro, setting text, color, number, or boolean values by track and clip index to update titles directly.
Change a Motion Graphics template property: text (string), color ('#rrggbb'), number or boolean
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes | ||
| fontSize | No | For text properties | |
| property | Yes | Property name or index from get_mogrt_properties (use the index when names repeat) | |
| clipIndex | Yes | ||
| trackIndex | Yes |
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 implies mutation but says nothing about permissions, reversibility, what happens on an invalid property/value, or whether the change applies only to the placed instance. No output schema exists to fill the gap.
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?
A single front-loaded sentence with no filler, and the value-format detail is placed where it is most needed. It is efficient, though wasted opportunity rather than wasted words is the issue.
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 5-parameter mutation with no annotations and no output schema, the description leaves the agent without the context needed to locate the target template (track/clip indices) or to know how to discover valid property identifiers. It covers only the value payload.
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 coverage is 40% across five parameters. The description usefully clarifies that a string value means text and specifies the '#rrggbb' color format (and the schema's array-of-numbers option is omitted), but it says nothing about trackIndex, clipIndex, or fontSize, which are the addressing parameters an agent must get right.
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?
States a specific verb and resource ('Change a Motion Graphics template property') and enumerates the accepted value types. It does not distinguish itself from the nearby get_mogrt_properties or set_effect_property siblings, but an agent can tell what it mutates.
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?
No when-to-use guidance, no prerequisites (the template presumably must already be placed on a timeline clip), and no mention of pairing with get_mogrt_properties to discover property names/indices before calling. The sibling list contains get_mogrt_properties, but the description never routes there.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.