Skip to main content
Glama

Title Card

title_card
Destructive

Generate a silent clip of centered text on a solid background to insert into highlight assemblies; warnings report characters the chosen font cannot render.

Instructions

Generate a title card clip (centered text on a solid background, silent audio track) to stitch in with assemble_highlights. Uncoverable characters are reported in warnings.

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_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgNoBackground color (default black).
fpsNoCard fps (default 30).
boldNoUse the bold weight (default true).
textYesTitle text. Multiple lines are allowed (use \n).
widthNoCard width (default 1920).
heightNoCard height (default 1080).
outputNoOptional output path. Defaults under SCREENCAST_HOME/edits.
durationNoCard length in seconds (default 3).
fontFileNoFont: a .ttf/.otf/.ttc path or a C:\Windows\Fonts file name. Default: bundled Inter, with a covering system font for scripts it lacks (CJK, emoji, Arabic, ...).
fontSizeNoText size in px (default 96).
fontColorNoText color (default white).
overwriteNoAllow replacing an existing file at the output path (default false).

Output Schema

NameRequiredDescriptionDefault
outputPathYesPath of the file written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.47.0
    • addedInput schema / properties / fontFile
      Added value: +{
      +  "description": "Font: a .ttf/.otf/.ttc path or a C:\\Windows\\Fonts file name. Default: bundled Inter, with a covering system font for scripts it lacks (CJK, emoji, Arabic, ...).",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "outputPath": {
      +      "description": "Path of the file written.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "outputPath"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.32.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds behavior beyond the annotations: the output is a real clip with a silent audio track (important for downstream concat/assembly) and unsupported glyphs surface as warnings rather than failing. It does not explain why the tool is flagged destructive (file creation at an output path, overwriting guarded by the overwrite param), which the schema partially covers.

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?

Two sentences, zero waste, with the core artifact description front-loaded and the caveat about warnings placed second. Nothing redundant with the schema or annotations.

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

Completeness4/5

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

All 12 parameters are documented in the schema and an output schema exists, so the description need not cover them. It covers the artifact's nature, audio characteristic, and error surface; a note about where the file lands or failure modes would make it complete.

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 100%, so baseline is 3. The description adds meaning by noting text is centered on the background, that the audio is silent, and that unrenderable characters are reported — context that relates to fontFile fallback behavior and makes the text parameter's rendering model clearer.

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

Purpose5/5

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

States a specific verb (generate) and resource (title card clip) and describes the artifact precisely: centered text on a solid background with a silent audio track. That output specification is what distinguishes it from overlay/callout/xfade siblings, which modify existing media rather than create a standalone clip.

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

Usage Guidelines4/5

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

Gives a concrete intended use — stitch the result in with assemble_highlights — which tells the agent where this fits in a workflow. It does not say when to prefer e.g. overlay or burn_subtitles instead of a standalone card, so no explicit exclusions.

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