Skip to main content
Glama

Create text crawl

create_text_crawl

Generate animated text crawls, vertical credits rolls, or character-by-character typewriter effects inside a self-contained TouchDesigner network. Supports multi-line text, continuous looping, and configurable speed, color, and font size.

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 (single-string flash/pulse/slide) and create_text_overlay (a static, non-moving caption/title); 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
loopNoWhen true (default), the scroll position wraps so the text crawls/rolls continuously. When false, it plays once and stops at the end.
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
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.
colorNoRGB text colour as three 0–1 floats, e.g. [1,1,1] = white. Sets fontcolorr/g/b on the Text TOP.
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.
widthNoOutput resolution width in pixels (sets resolutionw on the Text TOP).
heightNoOutput resolution height in pixels (sets resolutionh 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.
font_sizeNoFont size in pixels (maps to the Text TOP's fontsizex parameter; fontsizey is set to the same value).
parent_pathNoParent COMP where the text-crawl container is created (default '/project1')./project1
Behavior5/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description goes beyond these by detailing internal mechanics (TextTOP, TransformTOP, expression parameters, continuous looping), return values (JSON block with detailed fields), and experimental caveats (substring expression unverified). 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured, front-loaded with the main function, followed by modes, technical details, and sibling differentiation. Every sentence adds value without redundancy. At approximately 120 words, it is concise yet comprehensive.

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 the complexity of three modes and multiple operators, the description covers all essential aspects: mode operation, underlying TOPs, scroll behavior, return values, and experimental warnings. No output schema exists, but the description explicitly documents the return JSON structure, making it complete for tool selection and invocation.

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 parameter descriptions. The tool description reinforces parameter usage context (e.g., speed fraction, loop wrapping) but does not add significant new semantic meaning beyond what the schema already provides. 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 the tool builds multi-line animated text crawls/tickers/credits rolls/typewriter reveals inside a self-contained baseCOMP. It explicitly distinguishes from siblings create_kinetic_text and create_text_overlay, establishing a specific verb-resource relationship.

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 provides explicit guidance on when to use this tool (multi-line copy, continuous scrolling, character-reveal) and when not to (use create_kinetic_text for single-string flash/pulse/slide, create_text_overlay for static captions). It also notes the experimental nature of the typewriter mode.

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