Skip to main content
Glama

Create 3D extruded text

create_text_3d

Create a 3D text scene with extruded glyphs, color, optional Y-axis spin, and render output. Ideal for title cards and lyric reveals.

Instructions

Build a self-contained 3D text scene: a Text SOP generates the glyph outlines, an Extrude SOP gives them depth (the depth parameter controls depthscale), and a Geometry COMP holds the pipeline with a Constant MAT for colour. A Camera, a Light, and a Render TOP complete the 3D render, output as a Null TOP. Optional continuous Y-axis spin (spin degrees/sec) is driven by a time expression on the Geometry COMP's ry parameter. Exposes Spin and Depth as live knobs. The classic signature look for title cards, lyric reveals, and 3D text drops — use create_kinetic_text instead for flat 2D animated text. Returns a summary plus a JSON block with the container path, created node paths, exposed controls, any node errors, warnings, and an inline preview image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoBase name for the self-contained container COMP (default 'text_3d').text_3d
parent_pathNoParent COMP path where the text-3D container is created (default '/project1')./project1
textNoThe text to render in 3D. Use \n for multiple lines.HELLO
depthNoExtrusion depth in geometry units (controls the Extrude SOP's depthscale). 0 = flat polygons, 0.2 = typical title-card look.
spinNoContinuous Y-axis rotation in degrees per second (0 = static). Driven by an expression on the Geometry COMP's ry parameter.
colorNoText material colour as a hex string ('#ffffff' = white). Sets the Constant MAT's colorr/g/b.#ffffff
resolutionNoRender TOP output resolution as [width, height] in pixels (default [1280, 720]).
Behavior4/5

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

Annotations already indicate non-destructive, open-world creation. The description adds value by detailing the pipeline (Text SOP, Extrude SOP, etc.), explaining the spin expression, and describing the return format. 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.

Conciseness5/5

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

The description is efficiently structured: purpose first, then pipeline details, parameter context, usage guidance, and return format. Every sentence adds value without redundancy.

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 no output schema, the description fully explains the return value (summary plus JSON block with paths, controls, errors, preview). It also covers node creation, parameter effects, and alternative tools, making it complete.

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 100% schema coverage, baseline is 3. The description adds meaning beyond schema for depth ('0 = flat polygons, 0.2 = typical title-card look') and spin ('driven by an expression'), though some parameters like name and parent_path are straightforward.

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 'Build a self-contained 3D text scene' and differentiates from the sibling tool create_kinetic_text, which is for flat 2D animated text. The verb+resource is specific and distinct.

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?

Explicitly states when to use: classic signature look for title cards, lyric reveals, and 3D text drops. Directs to use create_kinetic_text instead for flat 2D animated text, providing clear alternatives.

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