Skip to main content
Glama

add_text_overlay

Adds a text overlay or title to a Premiere Pro timeline using a MOGRT template. Fills up to four text fields, such as main title and subtitle, at a specified time and duration.

Instructions

Adds a text layer (title) over the video timeline. Requires a MOGRT (.mogrt) template file path. Supports up to 4 text fields (text, text2, text3, text4) — each populates the Nth "AE.ADBE Text" component in the MOGRT (e.g., for Basic Lower Third: text=main title, text2=subtitle).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText for the first AE text component in the MOGRT (typically the main title)
text2NoText for the second AE text component (e.g., subtitle of a lower third)
text3NoText for the third AE text component (if present)
text4NoText for the fourth AE text component (if present)
durationYesHow long the text should remain on screen in seconds (best-effort; the MOGRT's natural duration may take precedence)
mogrtPathNoAbsolute path to a .mogrt template file (required for text overlays)
startTimeYesThe time in seconds when the text should appear
sequenceIdYesThe sequence to add the text to
trackIndexYesThe video track to place the text on (0-indexed; create the track first via add_track if needed)
textPropertyNameNoOverride: explicit displayName of the property to write into. When set, only `text` is written (text2/text3/text4 are ignored) and the call fails if no property with that displayName exists. Use only when auto-detection picks the wrong field.
rollbackOnTextFailureNoIf true, remove the imported timeline Graphic when every requested text write fails. Defaults to false; the imported project item may remain in the Project panel.
Behavior3/5

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

With no annotations, the description carries the transparency burden. It discloses the MOGRT requirement and field mapping but omits side effects such as imported project items remaining (mentioned only in schema for rollbackOnTextFailure) and the best-effort nature of duration. These omissions prevent a higher score.

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-loading the main purpose and then providing necessary requirements and mapping details with no filler. Every sentence adds value.

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?

Given the tool's complexity (11 params) and rich schema, the description adequately explains the core behavior and the trickiest part (MOGRT text mapping). It doesn't cover all parameters, but the schema handles those, so this is complete enough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, providing a baseline of 3. The description adds extra meaning through the example 'Basic Lower Third' and clarifies how text/text2 etc. map to AE.ADBE Text components, going beyond the schema's individual parameter descriptions.

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 clearly states the tool's function: 'Adds a text layer (title) over the video timeline.' It further specifies the MOGRT requirement and the up-to-4-field mapping, distinguishing it from generic timeline or adjustment tools.

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 provides clear context by stating the MOGRT requirement and the intended text field usage. It does not explicitly list alternative tools or exclusions, but the prerequisite is implied sufficiently for a 4.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hetpatel-11/Adobe_Premiere_Pro_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server