Skip to main content
Glama

add_text

Overlays a title or custom text on a video clip between specified start and end times, with configurable position, style, and optional box.

Instructions

A title or any text on the video, from start to end seconds (default: the whole clip).

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": {
      "video": "<video>",
      "text": "<text>"
    },
    "name": "add_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxNo
endNo
textYes
startNo
styleNobold
videoYes
positionNotop

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations declare this is a non-destructive mutation (readOnlyHint=false, destructiveHint=false), so the safety profile is covered. The description adds only that the text spans start to end and defaults to the whole clip; it says nothing about whether the overlay is burned into the output, how it interacts with existing overlays, or what happens when start/end are omitted versus null.

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 compact sentence with the timing constraint front-loaded, but the terseness crosses into under-specification rather than efficiency given the seven-parameter surface.

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 seven-parameter mutation tool with no output schema and no per-parameter schema descriptions, the definition is far too thin. Nothing explains the styling, positioning, or box options, so an agent cannot call this correctly without guessing.

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

Parameters1/5

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

Schema description coverage is 0% across seven parameters. The description clarifies only start/end and their default span; it is silent on text, video, style, position, and box, and gives no format hints (e.g., time units beyond 'seconds', accepted position values) that the bare schema lacks.

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

Purpose3/5

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

The description identifies the resource (a title or text on the video) and the temporal scope, but it is a sentence fragment with no verb, so the agent must infer 'add/overlay'. Compared with siblings such as add_captions and add_logo, nothing in the text distinguishes an overlay title from captions or branding assets.

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 use this versus add_captions (subtitle text) or end_card, nor any prerequisites about the video being built or exported first. The only implied usage comes from the tool name itself.

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