Skip to main content
Glama

figma_create_frame

Create an auto-layout frame for app shells, content containers, cards, rows, or columns. Control direction, gap, padding, sizing, alignment, fills, strokes, and corner radius using design system variables or direct values.

Instructions

Create an auto-layout frame. Use for application shells, content containers, cards, rows, columns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesLayer name
parentNodeIdNoAppend to this parent. Omit to place on current page.
widthNo
heightNo
directionNoAuto-layout direction. NONE = no auto-layout.
gapNoGap between children. DS variable path (e.g., "spacing-3xl") preferred. Raw px number allowed in permissive mode only.
gapVariableNoDS spacing variable path for gap (e.g., "Spacing/spacing-3xl"). Bound via setBoundVariable. Preferred over raw gap number.
paddingNoUniform padding. DS variable path preferred. Raw px allowed in permissive mode only.
paddingVariableNoDS spacing variable path for uniform padding. Bound to all 4 sides via setBoundVariable.
paddingTopNo
paddingRightNo
paddingBottomNo
paddingLeftNo
primaryAxisSizingModeNoAUTO = hug contents along primary axis. Defaults to FIXED when width+height are set.
counterAxisSizingModeNoAUTO = hug contents along counter axis.
primaryAxisAlignItemsNo
counterAxisAlignItemsNo
fillVariableNoDesign token variable path for background fill, e.g. "Colors/Background/bg-primary".
fillHexNoFallback hex color if fillVariable is not available.
fillNoneNoSet true for no fill (transparent).
strokeVariableNoVariable path for border color.
strokeHexNoFallback hex for border color.
strokeWidthNoBorder width in px.
cornerRadiusNoCorner radius. DS variable path (e.g., "radius-xl") preferred. Raw px allowed in permissive mode only.
cornerRadiusVariableNoDS radius variable path (e.g., "Radius/radius-xl"). Bound via setBoundVariable. Preferred over raw cornerRadius number.
clipsContentNo
layoutGrowNo1 = fill remaining space in parent.
layoutAlignNo
xNo
yNo
Behavior3/5

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

Description states creation behavior but doesn't add beyond annotations. Annotations are neutral; no contradiction.

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?

Very concise, two sentences, no wasted words, front-loaded.

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 30 parameters and no output schema, the description only covers basic purpose and use cases. Lacks details on defaults, interactions, and return values.

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 60% with parameter descriptions. The tool description itself does not add significant parameter information beyond what's in the schema.

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?

Explicitly states it creates an auto-layout frame and provides concrete use cases (application shells, content containers, cards, rows, columns), distinguishing from sibling tools like figma_create_rectangle.

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?

Suggests use cases but lacks explicit guidance on when not to use it or alternatives. No mention of other creation tools.

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/miapre/mimic-ai'

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