Skip to main content
Glama

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.

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": {
      "projectId": "<projectId>",
      "text": "<text>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "add_text_overlay"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNotitle_card is an opening hook. lower_third is a speaker label (name and role on separate lines). overlay is generic on-video text.title_card
nameNo
sizeNoTitle-card size. Ignored for overlay.default
textYes
themeNoTitle-card look. classic_white is black text on a white card. Ignored for overlay.classic_white
projectIdYesUUID string.
layerIndexNo
startSecondsNo
idempotencyKeyYesRetry key. Reuse only with identical inputs.
durationSecondsNo
expectedRevisionNoExpected sequence revision, or null.

Output Schema

NameRequiredDescriptionDefault
txidYes
resultYes
replayedYes
revisionYes
warningsYes
projectIdYes
operationIdYes
baseRevisionYes
mutationReceiptYes
createdTimelineItemIdsYes
deletedTimelineItemIdsYes
affectedTimelineItemIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"title_card is an opening hook. overlay is generic on-video text."New value: +"title_card is an opening hook. lower_third is a speaker label (name and role on separate lines). overlay is generic on-video text."
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "overlay",
      -  "title_card"
      -]New value: +[
      +  "overlay",
      +  "title_card",
      +  "lower_third"
      +]
  2. Changed3 schema fields changed
    • 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"
      +}
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive write, so the safety profile is covered. The description adds almost nothing beyond that -- the second sentence ('black text on a white card') simply restates the classic_white enum default already in the schema, and it never mentions concurrency behavior (expectedRevision), placement, or what happens on a retry key.

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?

Two short sentences, front-loaded with the action and the timeline target. The trailing default-theme sentence is largely redundant with the schema and does not earn its place, but nothing else is wasted.

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?

This is an 11-parameter mutation tool with only 55% schema coverage and no annotation-independent behavioral detail. With an output schema present the return value needn't be explained, but timing, layering, and revision-conflict semantics are left entirely undocumented.

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 coverage is only 55% across 11 parameters, so the description would need to compensate but does not. It never explains text, name, layerIndex, startSeconds, or durationSeconds semantics, and the only parameter-adjacent content it offers duplicates the theme default already documented in the enum.

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 opens with a specific verb and resource -- 'Add an opening title card (hook) or generic text overlay to a project timeline' -- which tells an agent exactly what gets created and where. It distinguishes the two main modes (title card vs generic overlay) reasonably well, though it never names a sibling such as editor_text_set or add_transition to clarify boundaries.

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 only implied: the reader learns a title card is an 'opening hook' and overlay is 'generic text,' which hints at when each applies. There is no explicit when-to-use versus alternatives, no prerequisites, and no note about when to prefer other text tools in the catalog.

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.

Resources