Skip to main content
Glama

title_card

Insert an opening card with custom text or an image on a dark background and fade it into the video to introduce the clip.

Instructions

A card at the START: text and/or a picture on a dark background, faded into the video.

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>"
    },
    "name": "title_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
imageNo
videoYes
secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description adds useful visual behavior (dark background, faded into the video, placed at the start) but does not say whether it overwrites the opening frames, whether it extends or shortens the clip, or what happens when text and image are both supplied.

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?

A single front-loaded sentence with no filler; the position constraint is stated first and the visual outcome second. It is tight, though the capitalized 'START' is the only structural cue.

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 mutation tool with four undocumented parameters and no output schema, the definition is too thin: duration, target video, and the text/image combination behavior are all left unknown. The annotations cover safety but not the operational details an agent needs to call it correctly.

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 0%, so the description must carry parameter meaning and largely fails: 'text' and 'picture' map loosely to two fields, but 'seconds' (default 2) and 'video' go entirely unmentioned, and no formats or defaults are given. An agent would not learn from the definition that the card has a configurable duration.

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 states a specific resource -- a title card -- and pins its position with 'at the START', which implicitly distinguishes it from the sibling end_card. The verb is not explicit (it says what the card is, not that the tool adds/creates it), so an agent must infer the operation, but the object and placement are unambiguous.

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?

Placement at the start implies the use case and contrasts with end_card by name-free inference, but there is no explicit when-to-use, no prerequisite stating the video must already exist, and no exclusion such as how it interacts with add_text or add_logo. Usage is implied rather than stated.

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