Skip to main content
Glama
neozhehan

Figma Edit MCP

Set Auto Layout

node_set_auto_layout
Idempotent

Set auto-layout properties for a frame: mode, padding, spacing, alignment, and sizing, all in one call.

Instructions

Configure a frame's auto-layout (mode, padding, spacing, alignment, sizing) in one unified setter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the frame to modify
nodeNameYesName of the node to modify
layoutModeNoLayout mode for the frame
layoutWrapNoWhether the auto-layout frame wraps its children
paddingTopNoTop padding value
itemSpacingNoDistance between children. Note: This value will be ignored if primaryAxisAlignItems is set to SPACE_BETWEEN.
paddingLeftNoLeft padding value
paddingRightNoRight padding value
paddingBottomNoBottom padding value
counterAxisSpacingNoDistance between wrapped rows/columns. Only works when layoutWrap is set to WRAP.
layoutSizingVerticalNoVertical sizing mode (HUG for frames/text only, FILL for auto-layout children only)
counterAxisAlignItemsNoCounter axis alignment (MIN/MAX = top/bottom in horizontal, left/right in vertical)
primaryAxisAlignItemsNoPrimary axis alignment (MIN/MAX = left/right in horizontal, top/bottom in vertical). Note: When set to SPACE_BETWEEN, itemSpacing will be ignored as children will be evenly spaced.
layoutSizingHorizontalNoHorizontal sizing mode (HUG for frames/text only, FILL for auto-layout children only)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the modified frame
Behavior3/5

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

Annotations include openWorldHint and idempotentHint, providing basic safety and retry context. The description adds no behavioral details beyond the tool's function—no mention of side effects, constraints, or interaction between parameters.

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?

A single sentence that is front-loaded with the key verb and resource, and expands on specifics. 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 complexity (14 parameters, many with enums) and presence of an output schema, the description adequately captures the tool's purpose. More detail on default values or interactions would be beneficial but not essential.

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% with each parameter having a description. The description adds no per-parameter meaning beyond the schema, simply summarizing the overall purpose.

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 configures a frame's auto-layout, listing specific aspects (mode, padding, spacing, alignment, sizing) and calling it a 'unified setter'. This distinguishes it from sibling tools like node_set_fill or node_set_stroke, which target different properties.

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 implies usage as a combined setter but provides no explicit guidance on when to use this tool versus alternatives (e.g., individual property setters). No exclusions or when-not-to-use context is given.

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/neozhehan/figma-edit-mcp'

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