Inserts a .mogrt file onto a specified video track with start time and duration, enabling template-based graphics placement on the Premiere Pro timeline.
Add a Motion Graphics Template (.mogrt) to the timeline
| Name | Required | Description | Default |
|---|---|---|---|
| duration | Yes | Duration in seconds | |
| mogrtPath | Yes | Full path to the .mogrt file | |
| startTime | Yes | Start time in seconds | |
| trackIndex | Yes | Video 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 for a mutation tool. It does not disclose whether the target track must exist, whether insertion overwrites existing clips, permission requirements, or what happens on invalid track indices or paths.
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 single sentence is front-loaded with the action and resource, and there is no wasted text. Its brevity is appropriate, though the definition is under-specified rather than optimally structured.
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 four-parameter mutation tool with no annotations and no output schema, the description is too sparse. It omits prerequisites, side effects, error conditions, and return behavior, leaving the agent to infer how insertion interacts with existing timeline content.
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 100%, and all four required parameters have descriptions in the schema, so the schema already does the heavy lifting. The tool description adds no additional meaning about units, acceptable index ranges, or path format beyond what is in the schema.
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 (add) and resource (.mogrt) and scopes it to the timeline. It is clear enough to distinguish from import_mogrt by implication, though it does not explicitly name or contrast sibling timeline insertion tools such as add_clip_to_timeline.
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?
Usage is implied by 'to the timeline': the agent can infer this inserts a template into an existing sequence rather than importing it. However, there is no explicit guidance on when to use this versus import_mogrt, add_clip_to_timeline, or set_mogrt_property after insertion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.