Skip to main content
Glama

filmcraft_generate_lower_third

Creates an animated lower third overlay for speakers or chapters directly on a timeline track, combining a title and subtitle with a custom accent color at a set start time.

Instructions

Uses HyperFrames to generate an animated Lower Third graphic overlay for speakers or chapters.

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": {
      "primaryText": "<primaryText>",
      "secondaryText": "<secondaryText>"
    },
    "name": "filmcraft_generate_lower_third"
  }
}

Input Schema

NameRequiredDescriptionDefault
accentColorNoHex accent color for the graphic bar#8b5cf6
primaryTextYesMain title / speaker name
targetTrackNoTimeline video track to place the graphic on (default V2)V2
startTimeSecNoTimeline start position in seconds
secondaryTextYesSubtitle / job title / chapter description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It only says the tool generates an animated graphic via HyperFrames; it never discloses that this inserts a clip onto a timeline track (implied by targetTrack/startTimeSec), whether the action mutates the project, whether it requires an open project, or whether it is undoable. That is a major gap for a project-mutating tool.

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 'Uses HyperFrames' clause is marginal implementation detail, but the sentence stays tight overall.

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?

With no annotations and no output schema, the description needed to carry the safety and behavior profile itself. It omits the return value, the fact that a graphic is placed on a video track at a given time, and any prerequisites — leaving an agent guessing how this affects the timeline.

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

Parameters3/5

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

Schema description coverage is 100%, with every parameter already documented in the schema (primaryText, secondaryText, accentColor, targetTrack, startTimeSec). The description adds no extra meaning about parameter semantics, so the baseline 3 applies.

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?

Names a specific verb ('generate') and resource ('animated Lower Third graphic overlay'), and even cites the use case (speakers or chapters). It does not distinguish itself from the sibling filmcraft_generate_title_card, so an agent must infer the split from the names alone.

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?

'for speakers or chapters' implies the usage context, giving some signal about when to reach for this tool. But it names no alternative and no exclusion criteria (e.g., 'use generate_title_card for full-screen titles instead'), so the when-to-use versus sibling choice is left to inference.

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