Skip to main content
Glama

Add text

add_text

PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. Burn a designed motion-graphics TEXT template over a PROGRAM-time window — separate from captions (spoken words) and overlays (media). Templates: 'title' (big centered opening card), 'subtitle' (support line under a title), 'lower_third' (name/context bar, interviews), 'callout' (short pointed label), 'big_number' (a huge stat — '10x', '$40K'), 'quote' (a quoted line), 'chapter' (section marker). x/y override the template's position (fractions of the frame); size_scale 0.4-3.0; color/accent_color '#RRGGBB'; font from the bundled families (exact name, e.g. 'Anton'); entrance/exit: 'none' (INSTANT — the text is simply there at frame one and simply gone at the end, no animation at all; use when the user wants no effect), fade, pop, slide_up, blur_in, whip, rise, drop, plus 'typewriter' (entrance only); uppercase forces casing; box adds a backing panel. motion is the general primitive for authored x/y/scale/rotation/opacity curves in LOCAL seconds: it can express a coherent drift, arc, settle, punch, spin or fade instead of choosing a named preset. When motion is present, omit entrance/exit. Use for text the user dictates — titles, labels, stats; spoken-word captions stay with add_captions. This text item owns caption suppression for its live window, so enabling captions before or after cannot stack two word layers and removing the text restores those captions automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
boxNo
endYes
exitNo
fontNo
textYes
colorNo
startYes
motionNoElement-local motion curves. t is seconds from this text's own start; x/y are frame fractions, scale is relative, rotation is degrees, opacity is 0..1.
entranceNo
templateNo
uppercaseNo
project_idYesRequired immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess.
size_scaleNo
accent_colorNo
motion_motifNoActive Blueprint motion motif id this event executes; never 'hold'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses a non-obvious side effect: this text item owns caption suppression for its live window, preventing stacked word layers and automatically restoring captions when removed. This goes beyond the minimal annotations and gives the agent a clear mental model of the tool's impact.

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

Conciseness4/5

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

The description is dense and information-rich, using lists and semicolons to organize options. It is longer than average, but every sentence adds value (e.g., explaining coordinate systems, edge cases, and the motion vs. preset decision). The structure is coherent and front-loaded with the core purpose.

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 complexity (17 parameters, nested objects, no output schema), the description is largely complete: it covers the main behaviors, constraints, and relationships with sibling tools. It lacks some details like return value structure, but since no output schema is provided, this is acceptable. The description effectively sets the tool in context.

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?

The schema description coverage is low (18%), but the tool description compensates by explaining many parameters: x/y override position, size_scale range (0.4–3.0), color/accent_color format, font families, entrance/exit presets, and the motion curve semantics (units, coordinate system). A few parameters (e.g., 'motion_motif') are only described in the schema and not in the description, but the overall coverage is strong.

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 that this tool burns a motion-graphics text template into a video window, explicitly distinguishing it from captions and overlays. It also specifies the intended use cases (dictated text like titles, labels, stats) in a concise way.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus alternatives (add_captions for spoken words, add_overlay for media) and explains the relationship between 'motion' and preset entrance/exit animations. It also clarifies that 'motion' should be used instead of named presets when authoring custom curves.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.