Skip to main content
Glama

Create kinetic text

create_kinetic_text

Create animated kinetic typography overlays that flash, pulse, or slide over a background, driven by a rate-controlled LFO for live VJ lyric effects.

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. 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. Output is a Null TOP. 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.

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_controlsNoExpose live Text / Size / Color / Rate controls bound to the right node parameters.
parent_pathNo/project1
Behavior4/5

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

The description details the animation mechanism (LFO CHOP, TOPs used, compositing) and output (Null TOP). It goes beyond annotations by explaining behavioral traits like the square wave for flash and the ability to bind to beats. No contradiction with annotations.

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 with a clear opening sentence, followed by technical details. It is relatively lengthy but each sentence adds value; could be slightly more concise but remains effective.

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?

The description provides comprehensive context for a complex tool with 8 parameters, no output schema, and minimal annotations. It explains the output (Null TOP), compositing behavior, and v1 limitations, making the tool fully understood.

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?

With 88% schema coverage, the description adds significant context beyond the input schema, such as explaining how each mode (flash, pulse, slide) behaves internally and the role of input_path. This helps the agent understand parameter interactions.

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 explicitly states it builds a self-contained animated/kinetic typography layer for a live VJ lyric-flash effect. It differentiates itself from siblings like create_text_overlay by focusing on animation (flash, pulse, slide).

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?

The description provides a clear use case (live VJ lyric-flash) but does not explicitly exclude alternatives or state when not to use. It hints at limitations (free-running for v1) but lacks direct guidance on choosing this tool over siblings.

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