BlitzReels Video Editor

Add Title Card

add_text_overlay

Idempotent

Add an opening title card (hook) or generic text overlay to a project timeline. Defaults to classic white: black text on a white card.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No	title_card is an opening hook. overlay is generic on-video text.	title_card
`name`	No
`size`	No	Title-card size. Ignored for overlay.	default
`text`	Yes
`theme`	No	Title-card look. classic_white is black text on a white card. Ignored for overlay.	classic_white
`projectId`	Yes	UUID string.
`layerIndex`	No
`startSeconds`	No
`idempotencyKey`	Yes	Retry key. Reuse only with identical inputs.
`durationSeconds`	No
`expectedRevision`	No	Expected sequence revision, or null.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`txid`	Yes
`result`	Yes
`replayed`	Yes
`revision`	Yes
`warnings`	Yes
`projectId`	Yes
`operationId`	Yes
`baseRevision`	Yes
`mutationReceipt`	Yes
`createdTimelineItemIds`	Yes
`deletedTimelineItemIds`	Yes
`affectedTimelineItemIds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 17, 2026

addedInput schema / properties / kind

Added value: +{
+  "default": "title_card",
+  "description": "title_card is an opening hook. overlay is generic on-video text.",
+  "enum": [
+    "overlay",
+    "title_card"
+  ],
+  "type": "string"
+}

addedInput schema / properties / size

Added value: +{
+  "default": "default",
+  "description": "Title-card size. Ignored for overlay.",
+  "enum": [
+    "compact",
+    "default",
+    "bold"
+  ],
+  "type": "string"
+}

addedInput schema / properties / theme

Added value: +{
+  "default": "classic_white",
+  "description": "Title-card look. classic_white is black text on a white card. Ignored for overlay.",
+  "enum": [
+    "classic_white",
+    "legend_white",
+    "white_black_outline",
+    "stacked_black_white",
+    "red_on_black",
+    "black_on_yellow",
+    "red_block"
+  ],
+  "type": "string"
+}

First observedAug 5, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the agent knows this is a mutating but safe operation. The description adds only the default theme ('classic white') and does not disclose other behavioral traits like interaction with existing timeline items or the impact of layerIndex. With annotations covering the core safety profile, a 3 is appropriate.

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 a single, efficient sentence that immediately states the tool's purpose and its default. No wasted words; it front-loads the core action and resource.

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 tool with 11 parameters, including two modes (overlay vs title_card) and several parameters that are ignored based on the mode, the description is too thin. It does not explain when to use overlay vs title_card, nor does it mention that certain parameters (size, theme) are ignored for overlay. Since an output schema exists, return values are covered, but the usage context is incomplete for such a configurable tool.

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

Parameters2/5

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

Schema description coverage is 55%, so a significant portion of parameters (name, layerIndex, startSeconds, durationSeconds, text) lack descriptions in the schema. The tool description adds no parameter guidance beyond mentioning the default theme, which is already in the schema. It fails to compensate for the undocumented parameters, making this a weak area.

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 clearly states the verb 'Add' and the resource 'opening title card (hook) or generic text overlay to a project timeline,' which is specific and unambiguous. It does not explicitly differentiate from sibling tools like timeline_media_add or add_transition, but the purpose is clear enough for an agent to understand what this tool does.

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?

The description gives no explicit guidance on when to use this tool versus alternatives, nor does it mention scenarios where another tool would be more appropriate. The distinction between 'overlay' and 'title_card' is only hinted at by the parenthetical, but no concrete usage context is provided.

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

All BlitzReels Video Editor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?