Skip to main content
Glama
mhue26

Talk to Figma MCP

by mhue26

set_layout_mode

Set a Figma frame's layout mode and wrap behavior. Specify horizontal or vertical arrangement, or disable layout, and control whether children wrap to the next line.

Instructions

Set the layout mode and wrap behavior of a frame in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the frame to modify
layoutModeYesLayout mode for the frame
layoutWrapNoWhether the auto-layout frame wraps its children
Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It does not mention side effects, preconditions (e.g., node must be a frame), or what happens when layoutMode is NONE or when layoutWrap is set with NONE. For a mutation tool, this is a significant gap.

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?

The description is a single, front-loaded sentence with no filler. Every word contributes to the meaning, and it is appropriately sized for a simple setter tool.

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?

Although the schema fully documents parameters, the description lacks usage context, behavioral details (e.g., constraints on layoutWrap), and any mention of expected outcomes or side effects. With no annotations and no output schema, this minimal description is incomplete for an agent to invoke the tool confidently in diverse scenarios.

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?

The schema covers 100% of parameters with descriptions and enums. The description echoes 'layout mode and wrap behavior' but adds no new semantic details beyond what the schema already provides, so it stays at the baseline for effective schema coverage.

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 states clearly that the tool sets layout mode and wrap behavior on a frame in Figma, using a specific verb and resource. The mention of 'layout mode and wrap behavior' distinguishes it from other set_* sibling tools like set_padding or set_layout_sizing.

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?

The description provides no when-to-use guidance, no exclusions, and no references to alternative tools. It does not mention conditions like 'use when the frame has auto-layout enabled' or contrast with other layout-related setters.

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

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