figma-mcp-go

set_auto_layout

Destructive

Set or update auto-layout properties on a Figma frame. Configure direction, padding, spacing, alignment, and wrapping.

Set or update auto-layout (flex) properties on an existing frame.

TableJSON Schema

Name	Required	Description
`nodeId`	Yes	Frame node ID in colon format e.g. '4029:12345'
`layoutMode`	No	Auto-layout direction: HORIZONTAL, VERTICAL, or NONE
`layoutWrap`	No	Wrap behaviour: NO_WRAP or WRAP
`paddingTop`	No	Top padding
`itemSpacing`	No	Gap between children
`paddingLeft`	No	Left padding
`paddingRight`	No	Right padding
`paddingBottom`	No	Bottom padding
`counterAxisSpacing`	No	Gap between wrapped rows/columns (only when layoutWrap is WRAP)
`counterAxisAlignItems`	No	Cross-axis alignment: MIN, CENTER, MAX, or BASELINE
`counterAxisSizingMode`	No	Cross-axis sizing: FIXED or AUTO (hug)
`primaryAxisAlignItems`	No	Main-axis alignment: MIN, CENTER, MAX, or SPACE_BETWEEN
`primaryAxisSizingMode`	No	Main-axis sizing: FIXED or AUTO (hug)

B3.2/5.0

Behavior2/5

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

Description merely restates mutability; annotations note destructiveHint, but no added context on overwrite behavior or failure modes.

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?

Single sentence, front-loaded, no redundancy.

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?

Minimal description for a complex 13-param tool; lacks explanation of defaults, interaction effects, or validation rules.

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%, description adds no extra meaning beyond param names and types.

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?

Clear verb 'Set or update' and resource 'auto-layout properties on an existing frame'. Unambiguous and distinct from sibling tools.

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 guidance on when to use this tool vs alternatives, no prerequisites or context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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