Skip to main content
Glama
sso-ss

figma-unified-mcp

by sso-ss

figma_create_component

Create reusable Figma components with auto-layout, strokes, and nested children support. Define dimensions, colors, padding, and alignment to build scalable design systems.

Instructions

Create a reusable component with full auto-layout, stroke, and nested children support.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
nameYes
widthYes
heightYes
opacityNo
paddingNo
childrenNoNested children: [{type:'TEXT',content:'Hi',...}]
parentIdNo
fillColorNoColor as hex string "#RRGGBB" or object {r,g,b,a?} with 0-1 values
autoLayoutNo
layoutWrapNo
paddingTopNo
descriptionNo
itemSpacingNo
paddingLeftNo
strokeAlignNo
strokeColorNoColor as hex string "#RRGGBB" or object {r,g,b,a?} with 0-1 values
clipsContentNo
cornerRadiusNo
paddingRightNo
strokeWeightNo
paddingBottomNo
counterAxisAlignNo
primaryAxisAlignNo
counterAxisSizingNo
primaryAxisSizingNo
counterAxisSpacingNo
Behavior2/5

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

No annotations are present, so the description must carry the burden of disclosing side effects and behavior. It only asserts capability ('full support') without explaining what creating a component actually does in Figma, such as library implications, required permissions, or default behaviors. This is insufficient for a complex creation tool.

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. 'Create a reusable component' is immediately clear, and the feature list is compact. All words earn their place.

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?

Given the tool's complexity (28 parameters, no annotations, no output schema), the description is grossly incomplete. It omits crucial context such as return value, side effects on existing nodes, prerequisites like parentId requirements, and how component mutability works. The description provides only a surface-level promise of functionality.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 11% schema description coverage and 28 parameters, the description should compensate by explaining parameter semantics. It merely hints at auto-layout, stroke, and children feature areas, but does not clarify any specific parameter formats, defaults, or relationships. The schema already does more for children and colors than the tool description does.

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 'Create a reusable component' which is a specific verb+resource. The mention of 'full auto-layout, stroke, and nested children support' adds scope and helps differentiate from generic frame or rectangle creation tools, though it could be clearer about component vs instance semantics.

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 is provided on when to use this tool versus alternatives like figma_create_frame or figma_create_rectangle. With many similar creation siblings, the agent gets no context for selecting this tool.

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/sso-ss/figma-unified-mcp'

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