Skip to main content
Glama

Create kinetic text

create_kinetic_text

Generate animated text effects (flash, pulse, or slide) for live VJ lyric displays. Drive the animation with an LFO at a specified rate, compositing over a background or on transparent frame.

Instructions

Build a self-contained animated / kinetic typography layer — a word or line that flashes, pulses, or slides, the signature live-VJ lyric-flash effect. A Text TOP renders the text; an LFO CHOP at the given Rate (Hz) drives the animation: 'flash' gates a Level TOP's alpha/opacity hard on/off (a square wave — the text vanishes between flashes rather than turning black, so it pops cleanly in and out over a background), 'pulse' drives a Transform TOP's scale plus a Level TOP alpha fade (a sine, the text breathes), and 'slide' scrolls the Transform TOP's translate-X. Creates a new baseCOMP under parent_path holding the Text TOP, the LFO, the per-mode Transform/Level nodes, an optional Composite, and a Null output. With an input_path the text is composited OVER that source (pulled in by a Select TOP, so it can live in another container); without one it animates on a transparent frame. Rate is free-running for v1 — bind the LFO's frequency to a beat CHOP (or a Trigger to a detect_onsets channel) to lock the flashes to the tempo. This is for a single animated word/line; for a static caption or title use create_text_overlay, and for multi-line scrolling tickers/credits rolls/typewriter reveals use create_text_crawl. Returns a summary plus a JSON block with the container path, created node paths, the text/lfo/output paths, exposed controls, any node errors, warnings, and an inline preview image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoAnimation style: 'flash' = hard on/off blink (a square LFO gates the alpha/opacity — the classic lyric-flash, the text vanishes between flashes rather than going black); 'pulse' = breathing scale-up + alpha fade driven by a sine LFO; 'slide' = the text scrolls horizontally across the frame.flash
sizeNoFont size in pixels (drives the Text TOP's fontsizex / fontsizey).
textNoThe word or line to animate (the lyric flash). Rendered by a Text TOP. For multiple lines use \n.DUQUESA
colorNoText colour as a hex string ('#ffffff' = white). Sets the Text TOP's fontcolorr/g/b.#ffffff
rate_hzNoAnimation rate in cycles per second (Hz) — the LFO frequency. Free-running for v1; bind it to a beat CHOP to fire on the actual beat.
input_pathNoOptional absolute path of a source TOP to lay the text OVER. Pulled in via a Select TOP (TD wires don't cross containers) and composited under the text. If omitted, the text animates on a transparent frame.
parent_pathNoParent network where the kinetic-text container is created (default '/project1')./project1
expose_controlsNoWhen true (default), expose live Text / Size / Color / Rate controls bound to the right node parameters.
Behavior5/5

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

Annotations are basic (readOnlyHint=false, openWorldHint=true, destructiveHint=false). Description adds extensive behavioral details: how each mode works (square wave for flash, sine for pulse, translate-X for slide), compositing over input_path, free-running rate, creates nodes, returns summary and JSON. No contradictions.

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?

The description is well-structured: purpose first, then behavior, usage guidelines, output. Every sentence adds value, though it is lengthy. Could be slightly more concise but excellent in depth and organization.

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

Completeness5/5

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

Given the complexity (8 parameters, 3 modes, node creation) and no output schema, the description is remarkably complete: explains what it does, how it works, when to use, when not, parameter implications, output format (JSON with paths, errors, preview). No gaps.

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 detailed param descriptions. The tool description adds structural context (e.g., mode details) but does not significantly enhance per-parameter meaning beyond the schema. Baseline 3 is appropriate.

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?

The description clearly states it builds a self-contained animated/kinetic typography layer, with specific modes (flash, pulse, slide). It explicitly differentiates from sibling tools create_text_overlay and create_text_crawl, stating when each should be used.

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

Usage Guidelines5/5

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

Provides explicit when-to-use: 'single animated word/line', and when-not-to: 'static caption or title use create_text_overlay' and 'multi-line scrolling... use create_text_crawl'. Also gives guidance on binding rate to beat CHOP for tempo sync.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server