Skip to main content
Glama

title_add

Add styled text titles to DaVinci Resolve timelines at the playhead or a custom time, with template, font, color, position, track, and duration controls.

Instructions

Add a title at at (default: playhead) for duration seconds on track. template: a Fusion title name ('Text+', 'Background Reveal', 'Call Out', …) or prefix 'edit:' for Edit-page titles ('edit:Text', 'edit:Scroll'). Style: font ('Vazirmatn', 'Arial'), style ('Bold'), size (Text+ size ~0.05-0.2), color ('#ffcc00' or [r,g,b]), position [x,y] (0-1, center = [0.5,0.5]), plus raw Text+ inputs. Persian/Arabic text works in Text+. Placed titles not on V1/end are wrapped as compound clips (bin 'Titles (MCP)'); title_update still edits them.

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": "title_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo
fontNo
nameNo
sizeNo
textYes
colorNo
styleNo
trackNoV2
inputsNo
durationNo
positionNo
templateNoText+

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely non-obvious side effect: titles not on V1/end are silently wrapped as compound clips in bin 'Titles (MCP)'. It says nothing about whether the title must be rendered before it appears, what the call returns (name/id needed for title_update), failure modes for bad templates, or undo behavior — gaps that matter for a 12-parameter mutation.

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?

Placement essentials lead, followed by the template vocabulary and style formats, so the paragraph is front-loaded and dense with usable detail rather than filler. Minor clutter from the Persian/Arabic aside and the parenthetical example lists, but overall appropriate for a 12-parameter tool.

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

Completeness3/5

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

For a tool with no annotations and no output schema, the description covers most input semantics and one structural side effect, but leaves the agent guessing about the return value, whether `text` is mandatory, and what `name` does. Enough to make a reasonable call, not enough to call it confidently the first time.

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 0%, so the description must compensate, and it largely does: it defines `at` default, `template` values with concrete examples and the 'edit:' prefix convention, and formats/ranges for font, style, size (~0.05–0.2), color ('#ffcc00' or [r,g,b]), and position (0–1 normalized, center [0.5,0.5]). The `name` parameter and the required status of `text` are left undocumented, and track's default V2 is only in the schema.

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 first clause gives a specific verb and resource ('Add a title') plus placement defaults (at = playhead, duration, track), which is far beyond a restatement of the name. The closing note that placed titles become compound clips and that 'title_update still edits them' implicitly separates create from edit. It stops short of naming when to prefer this over generator_add or fusion_tool_add.

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

Usage Guidelines3/5

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

Usage is implied by the parameter elucidation and the offhand reference to title_update, but there is no explicit 'use this when…' vs 'use X instead' routing against the many sibling add-tools. The template prefix convention ('edit:') is the only branching guidance offered.

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