Skip to main content
Glama
haju-xp

figma-free-mcp

by haju-xp

create_text

Create a text element in Figma with custom content, position, font, and alignment. Specify optional parent, width, and resize behavior.

Instructions

Create a new text element in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX position (local coordinates, relative to parent)
yYesY position (local coordinates, relative to parent)
textYesText content
fontSizeNoFont size (default: 14)
fontWeightNoFont weight (e.g., 400 for Regular, 700 for Bold)
fontColorNoFont color in RGBA format
nameNoOptional name for the text node by default following text
parentIdNoOptional parent node ID to append the text to
textAlignHorizontalNoHorizontal text alignment. Use RIGHT for Arabic/RTL text.
textAutoResizeNoText resize behavior. Use HEIGHT for fixed-width text that wraps.
widthNoFixed width for the text node. Use with textAutoResize HEIGHT for wrapping text within a specific width.
Behavior2/5

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

No annotations are provided, and the description only indicates creation without disclosing side effects, permissions, required state (e.g., file openness), or return values.

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 a single, front-loaded sentence. It is efficient but could benefit from additional structure such as examples or notes given the 11 parameters.

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

Completeness2/5

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

Despite rich schema, the description fails to explain when to create vs. modify text, or to note that parentId is optional but may be needed, leaving significant gaps.

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 coverage is 100%, so baseline is 3. The description does not add parameter information, but the schema already describes each parameter adequately.

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 action 'Create' and the resource 'new text element in Figma', differentiating it from sibling tools like create_rectangle or set_text_content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No information is provided on when to use this tool versus alternatives such as create_shape_with_text or set_text_content, leaving the agent without usage 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/haju-xp/figma-free-mcp'

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