Skip to main content
Glama

Create kinetic text

create_kinetic_text

Create animated kinetic typography that flashes, pulses, or slides over a background or transparent frame. Drives text animation with an LFO at a given rate.

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. 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
textNoThe word or line to animate (the lyric flash). Rendered by a Text TOP. For multiple lines use \n.DUQUESA
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).
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.
expose_controlsNoWhen true (default), expose live Text / Size / Color / Rate controls bound to the right node parameters.
parent_pathNoParent network where the kinetic-text container is created (default '/project1')./project1
Behavior5/5

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

The description fully explains the tool's behavior: it creates a baseCOMP with Text TOP, LFO, per-mode nodes, and optional composite. It details each animation mode's waveform (square wave for flash, sine for pulse, translate-X for slide) and compositing logic. Annotations indicate creation (readOnlyHint=false) and non-destructive (destructiveHint=false), aligning with the description.

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 a single coherent paragraph that front-loads the purpose and then details behavior. While it is relatively long, every sentence adds value. Could be slightly more concise, but structure is logical and information-dense.

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?

Despite no output schema, the description explicitly lists the return value: a summary plus JSON block with container path, created node paths, text/lfo/output paths, exposed controls, errors, warnings, and preview image. It covers all aspects of the tool's operation, including compositing, animation modes, and parameter exposure.

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%, and the description adds meaning beyond the schema: e.g., explains that text is 'rendered by a Text TOP', mode details the waveform, input_path explains the Select TOP mechanism, rate describes free-running and binding. It goes beyond basic schema but lacks exhaustive examples for each parameter.

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 the tool creates a 'self-contained animated / kinetic typography layer' with specific modes (flash, pulse, slide), targeting a VJ lyric-flash effect. It distinguishes itself from other text tools like create_text_crawl or create_text_overlay by specifying the animation mechanics and use case.

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?

The description provides clear context for use (live VJ lyric-flash), mentions optional input_path for compositing over a source, and suggests binding to a beat CHOP. However, it does not explicitly mention when not to use this tool or compare to sibling tools like create_text_crawl or create_text_overlay.

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