Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_auto_layout

Set auto layout properties on any Figma node, including direction, padding, spacing, alignment, and wrap behavior. Adjust layout parameters like padding, item spacing, and alignment axes to precisely control node arrangement.

Instructions

Configure auto layout properties for a node in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to configure auto layout
layoutModeYesLayout direction
paddingTopNoTop padding in pixels
paddingBottomNoBottom padding in pixels
paddingLeftNoLeft padding in pixels
paddingRightNoRight padding in pixels
itemSpacingNoSpacing between items in pixels
primaryAxisAlignItemsNoAlignment along primary axis
counterAxisAlignItemsNoAlignment along counter axis
layoutWrapNoWhether items wrap to new lines
strokesIncludedInLayoutNoWhether strokes are included in layout calculations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed13 schema fields changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / counterAxisAlignItems
      Added value: +{
+  "description": "Alignment along counter axis",
+  "enum": [
+    "MIN",
+    "CENTER",
+    "MAX"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / itemSpacing
      Added value: +{
+  "description": "Spacing between items in pixels",
+  "type": "number"
+}
    • addedInput schema / properties / layoutMode
      Added value: +{
+  "description": "Layout direction",
+  "enum": [
+    "HORIZONTAL",
+    "VERTICAL",
+    "NONE"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / layoutWrap
      Added value: +{
+  "description": "Whether items wrap to new lines",
+  "enum": [
+    "WRAP",
+    "NO_WRAP"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / nodeId
      Added value: +{
+  "description": "The ID of the node to configure auto layout",
+  "type": "string"
+}
    • addedInput schema / properties / paddingBottom
      Added value: +{
+  "description": "Bottom padding in pixels",
+  "type": "number"
+}
    • addedInput schema / properties / paddingLeft
      Added value: +{
+  "description": "Left padding in pixels",
+  "type": "number"
+}
    • addedInput schema / properties / paddingRight
      Added value: +{
+  "description": "Right padding in pixels",
+  "type": "number"
+}
    • addedInput schema / properties / paddingTop
      Added value: +{
+  "description": "Top padding in pixels",
+  "type": "number"
+}
    • addedInput schema / properties / primaryAxisAlignItems
      Added value: +{
+  "description": "Alignment along primary axis",
+  "enum": [
+    "MIN",
+    "CENTER",
+    "MAX",
+    "SPACE_BETWEEN"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / strokesIncludedInLayout
      Added value: +{
+  "description": "Whether strokes are included in layout calculations",
+  "type": "boolean"
+}
    • addedInput schema / required
      Added value: +[
+  "nodeId",
+  "layoutMode"
+]
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description bears full burden. It only states 'Configure', without disclosing effects like whether existing properties are overridden, if the node must already have auto layout enabled, or any permissions needed. The description lacks behavioral detail beyond the action.

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 concise sentence that front-loads the purpose. No redundant or unnecessary words; every part contributes to clarity.

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?

With 11 parameters, no output schema, and no annotations, the description is incomplete. It omits return values, error conditions, preconditions (e.g., does the node need to be a frame?), and behavioral context. A more thorough description is needed for such a complex tool.

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 the baseline is 3. The description adds no additional meaning beyond the schema; parameters are already well-described in the schema (e.g., 'paddingTop', 'layoutMode'). No relational or conditional semantics are explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool configures auto layout properties for a Figma node. It specifies the verb 'Configure' and resource 'auto layout properties', distinguishing it from generic node property tools like set_node_properties. However, it could be more precise about the scope (e.g., 'for a given node').

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 versus alternatives. For instance, it does not clarify that this tool is specifically for auto layout settings, while other tools like set_node_properties might be used for general properties. There is no mention of prerequisites or when not to use it.

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

Deploy Server

Other Tools