Skip to main content
Glama
neozhehan

Figma Edit MCP

Create Frame

create_frame

Create a frame container with customizable position, size, fill, stroke, and auto-layout settings to structure design elements in Figma.

Instructions

Create a frame (container) with optional fill/stroke and full auto-layout configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX position
yYesY position
nameNoOptional name for the frame
widthYesWidth of the frame
heightYesHeight of the frame
parentIdYesParent node ID to append the frame to
fillColorNoFill color in RGBA format
layoutModeNoAuto-layout mode for the frame
layoutWrapNoWhether the auto-layout frame wraps its children
paddingTopNoTop padding for auto-layout frame
itemSpacingNoDistance between children in auto-layout frame. Note: This value will be ignored if primaryAxisAlignItems is set to SPACE_BETWEEN.
paddingLeftNoLeft padding for auto-layout frame
strokeColorNoStroke color in RGBA format
paddingRightNoRight padding for auto-layout frame
strokeWeightNoStroke weight
paddingBottomNoBottom padding for auto-layout frame
parentNodeNameNoName of the parent node to verify against
layoutSizingVerticalNoVertical sizing mode for auto-layout frame
counterAxisAlignItemsNoCounter axis alignment for auto-layout frame
primaryAxisAlignItemsNoPrimary axis alignment for auto-layout frame. Note: When set to SPACE_BETWEEN, itemSpacing will be ignored as children will be evenly spaced.
layoutSizingHorizontalNoHorizontal sizing mode for auto-layout frame

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the created frame
nameYesName of the created frame
Behavior3/5

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

The description provides no behavioral details beyond the obvious creation action. The openWorldHint annotation hints at non-deterministic behavior but the description does not elaborate.

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 extremely concise and front-loaded, conveying the essential purpose in a single sentence without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high parameter count and existence of an output schema, the description is adequate but lacks details about return values or behavior beyond creation.

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 baseline is 3. The description adds minimal context about optional fill/stroke and auto-layout but does not explain individual parameters beyond what schema already provides.

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 a frame container with optional styling and auto-layout, distinguishing it from sibling tools like create_shape and create_text.

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 for frames with auto-layout but does not explicitly state when to use this tool versus alternatives like create_shape or node_group.

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