Skip to main content
Glama

create_text

Destructive

Create a new text node on the current Figma page or inside a specific parent node. Automatically loads the font and returns the node ID and bounds for further editing.

Instructions

Create a new text node on the current page or inside a parent node. The font is loaded automatically before insertion. Returns the created node ID and bounds. Use set_text to update the content of an existing text node.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoX position in pixels (default 0)
yNoY position in pixels (default 0)
nameNoNode name shown in the layers panel (defaults to the text content)
textYesText content to display
fontSizeNoFont size in pixels (default 14)
parentIdNoParent node ID in colon format. Defaults to current page.
fillColorNoText color as hex e.g. #000000 (default black)
fontStyleNoFont style variant e.g. 'Regular', 'Bold', 'Italic', 'Medium', 'SemiBold' (default Regular). Must match an available style for the chosen fontFamily.
fontFamilyNoFont family name e.g. 'Inter', 'Roboto', 'SF Pro Display' (default Inter). Must be a font installed in Figma.
Behavior4/5

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

Annotations indicate write (readOnlyHint=false), destruction (destructiveHint=true), and openness (openWorldHint=true). Description adds value by stating font auto-loading and return of node ID and bounds.

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?

Two sentences: first states core purpose and behavior, second provides alternative and return info. Front-loaded and no wasted words.

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?

Given the tool creates a text node with many parameters, the description explains the creation scope and return values, while the schema covers parameters. No output schema, but return info is provided.

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 covers all 9 parameters with descriptions (100% coverage). Description adds no additional parameter details beyond the automatic font loading context.

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?

Clearly states verb 'create', resource 'text node', and scope 'on the current page or inside a parent node'. Distinguishes from sibling 'set_text' which updates existing.

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 says to use 'set_text' for updating, and mentions font is loaded automatically, providing when-not and context.

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/vkhanhqui/figma-mcp-go'

If you have feedback or need assistance with the MCP directory API, please join our Discord server