Skip to main content
Glama
Blyawon

tokensStudioMCP

by Blyawon

create_node

Create Figma nodes (frame, text, shape, SVG, image) with fill, stroke, auto-layout, and nested children to build entire UI trees in one call.

Instructions

Create a node in the live Figma file via the plugin: frame, rectangle, ellipse, line, text, autolayout (frame with flex), or instance (from a componentId). Auto-positions right of existing content unless x is given. Supports fill/stroke (hex, rgb(), hsl(), or 'none'), cornerRadius, opacity, and auto-layout props (layout='row'|'col', gap, padding, justify/items = start|center|end|between, sizingHorizontal/Vertical = HUG|FILL|FIXED). Text supports characters, fontSize, fontFamily, fontStyle. Pass children (array of nested create_node specs, same shape minus parentId) to build a WHOLE TREE in one call — e.g. a card frame with title + body + button. Also supports type='svg' ({svg: markup}), 'image' ({base64}), 'section', and in FigJam files 'sticky', 'connector' ({startNodeId,endNodeId}), 'shape'. Returns the new root node's id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
gapNo
svgNoSVG markup for type='svg'.
fillNo
nameNo
typeYes
itemsNo
widthNo
base64NoBase64 image bytes for type='image'.
heightNo
layoutNo
strokeNo
justifyNo
opacityNo
paddingNoNumber or CSS-style '8 16' / '8/16/8/16'.
childrenNoNested create_node specs (recursive). Child-only extras: sizingHorizontal/sizingVertical = HUG|FILL|FIXED.
fontSizeNo
parentIdNoAppend into this node instead of the page.
endNodeIdNo
fontStyleNo
shapeTypeNo
charactersNo
fontFamilyNo
componentIdNoFor type='instance'.
startNodeIdNo
cornerRadiusNo
strokeWeightNo
Behavior4/5

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

With no annotations, the description reveals key behaviors: auto-positioning unless x given, recursion via children, support for many types (svg, image, section, etc.), and returns root node id. However, lacks details on error handling, permissions, or limitations.

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 long but well-structured: begins with basic function, lists supported types, then details properties per type, and ends with nesting. Every sentence adds value, though some redundancy could be trimmed.

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 28 parameters and no output schema, the description covers the core purpose and property behavior. Missing details on required type and its enum values, but overall it equips an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is low (21%), but the description adds significant meaning: explains auto-positioning for x, padding CSS-style notation, children recursion, and sub-properties for each type (e.g., text: characters, fontSize). This compensates for missing schema descriptions.

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 it creates nodes in a live Figma file, listing many node types (frame, rectangle, ellipse, etc.). It distinguishes from sibling tools which are mostly tokens/themes/analysis related.

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

Usage Guidelines3/5

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

The description explains auto-positioning and property support but does not explicitly state when to use this tool versus alternatives like node_action or canvas_audit. No when-not or exclusion criteria.

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/Blyawon/tokensStudioMCP'

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