Skip to main content
Glama

Create text crawl

create_text_crawl

Creates animated text crawls, rolling credits, or typewriter reveals in TouchDesigner. Supports continuous horizontal scroll, vertical roll, and character-by-character display.

Instructions

Build a multi-line animated text crawl / ticker / credits roll / typewriter reveal inside a self-contained baseCOMP. Three modes: 'crawl_horizontal' = continuous left-scrolling ticker tape (news-ticker style); 'roll_vertical' = upward credits roll (use \n to separate lines); 'typewriter' = text is revealed character-by-character from left to right (EXPERIMENTAL — the substring expression on a textTOP text par is unverified across TD builds). A textTOP renders the content; a transformTOP animates position via an EXPRESSION parameter (crawl/roll modes) or the textTOP text par is set to a time-sliced substring expression (typewriter mode). The scroll wraps continuously (loop=true, default) so the text re-enters from the opposite edge. Outputs a nullTOP 'out' as a stable handle. Differs from create_kinetic_text which is single-string flash/pulse/slide; this tool handles multi-line copy, continuous scrolling, and character-reveal. Returns a JSON block with container path, output_top, text_top, transform_top, mode, line count, and any per-step warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_pathNoParent COMP where the text-crawl container is created (default '/project1')./project1
nameNoName for the baseCOMP container that holds the crawl network.text_crawl
textYesThe text content to display. Use \n to separate multiple lines (e.g. for a ticker or credits roll). All lines are fed to a single Text TOP.
modeNoAnimation style: 'crawl_horizontal' = text scrolls continuously left across the frame (ticker-tape); 'roll_vertical' = text rolls upward (credits roll); 'typewriter' = text is revealed one character at a time from left to right — EXPERIMENTAL (the substring expression on a textTOP par is UNVERIFIED across TD builds).crawl_horizontal
speedNoScroll speed as a fraction of the output resolution per second. 0.1 = the text travels one full screen-width per 10 s. Drives the Transform TOP position expression.
font_sizeNoFont size in pixels (maps to the Text TOP's fontsizex parameter; fontsizey is set to the same value).
colorNoRGB text colour as three 0–1 floats, e.g. [1,1,1] = white. Sets fontcolorr/g/b on the Text TOP.
bg_alphaNoBackground alpha [0–1]. 0 = fully transparent background (text over black/transparent). The par name is probed: 'alphabg' is tried first, then 'bgalpha' — UNVERIFIED across TD builds.
widthNoOutput resolution width in pixels (sets resolutionw on the Text TOP).
heightNoOutput resolution height in pixels (sets resolutionh on the Text TOP).
loopNoWhen true (default), the scroll position wraps so the text crawls/rolls continuously. When false, it plays once and stops at the end.
Behavior5/5

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

The description discloses experimental status of typewriter mode, unverified par names for bg_alpha, continuous looping behavior, and the output structure. It adds significant context beyond annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) with 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, front-loading the main purpose, then detailing modes, technical implementation, and differentiation. It is informative without being overly verbose, though a minor trim could improve conciseness.

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

Completeness4/5

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

The description covers all 11 parameters, explains return values (JSON with specific fields), and includes warnings about experimental features. Given no output schema, this is sufficient for the tool's complexity.

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?

All 11 parameters are fully described in the schema (100% coverage). The description adds extra context such as mode enum explanations, speed fraction meaning, font color mapping, and bg_alpha par name probing, providing meaning beyond schema fields.

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 builds multi-line animated text crawl/ticker/credits/typewriter in a baseCOMP. It lists three modes with specific behaviors and explicitly differentiates from sibling create_kinetic_text, which handles single-string animations.

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?

The description explicitly contrasts with create_kinetic_text, indicating when to use this tool (multi-line, continuous scrolling, character-reveal) vs alternatives. It also implies usage for text crawls, rolls, and typewriter effects.

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