Skip to main content
Glama

add_text

Add a text title graphic clip to a video timeline, with controls for text, start time, duration, position, font, size, color, alignment, and target track.

Instructions

Add a text title (graphic clip) on the timeline.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "add_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontNo
sizeNoFont size in px
textYes
timeNoStart time, in seconds
alignNoHow the text sits around its anchorcenter
colorNoFill colour, #rrggbb
projectNoPath to the .fcproj project file; omit to edit the FilmCraft app connected with connect_app
durationNoSeconds
positionNoAnchor [x, y] in pixels on the first baseline; default frame centre
trackIndexNoVideo track index (0 = V1); default: the track above the clips

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=false, so the agent already knows this mutates local state; the word 'Add' is consistent with that. The description adds no behavioral detail beyond the annotations, such as which track is targeted by default, what happens if the track is occupied, or whether the edit can be undone.

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

Conciseness3/5

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

A single front-loaded sentence with zero filler, which is structurally clean. However, at ten parameters and a mutating operation, this length is under-specified rather than truly concise.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with ten parameters, no output schema, and a choice between editing an explicit .fcproj file or the connected app, one sentence is not enough. The agent gets no signal about return values, track placement effects, or interaction with connect_app.

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 description coverage is 80%, so defaults, units, and enums (align, position, trackIndex default) are already documented in the schema. The description adds nothing about parameters, so the baseline 3 applies.

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

Purpose4/5

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

The description uses a specific verb and resource ('Add a text title (graphic clip) on the timeline'), so an agent knows exactly what object is created. It does not differentiate from siblings such as add_clip, add_transition, or add_marker, which also create items on the timeline.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool versus add_clip or other timeline-insertion tools, and no mention of prerequisites such as connecting an app or supplying a project path. Usage must be inferred entirely from the name and sibling list.

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