Claude Talk to Figma MCP

Overview Schema Source Related Servers Discussions Admin

create_frame

Create a new frame in Figma with specified position, size, and optional styling. Set parent page via ID, define coordinates, dimensions, fill, and stroke to build your design layout.

Instructions

Create a new frame in Figma

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "create_frame"
  }
}

Input Schema

Name	Required	Description
`x`	Yes	X position (local coordinates, relative to parent)
`y`	Yes	Y position (local coordinates, relative to parent)
`width`	Yes	Width of the frame
`height`	Yes	Height of the frame
`name`	No	Optional name for the frame
`parentId`	No	Parent node ID. REQUIRED — server enforces this. Use page node ID for top-level elements. Get page IDs via get_pages tool.
`fillColor`	No	Fill color in RGBA format
`strokeColor`	No	Stroke color in RGBA format
`strokeWeight`	No	Stroke weight

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.8.2May 1, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / fillColor / additionalProperties
```
Added value: +false
```

changedInput schema / properties / parentId / description

Previous value: -"Optional parent node ID to append the frame to"New value: +"Parent node ID. REQUIRED — server enforces this. Use page node ID for top-level elements. Get page IDs via get_pages tool."

addedInput schema / properties / strokeColor / additionalProperties
```
Added value: +false
```

changedInput schema / properties / x / description

Previous value: -"X position"New value: +"X position (local coordinates, relative to parent)"

changedInput schema / properties / y / description

Previous value: -"Y position"New value: +"Y position (local coordinates, relative to parent)"

Changed11 schema fields changedv1.0.0Jan 3, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / fillColor

Added value: +{
+  "description": "Fill color in RGBA format",
+  "properties": {
+    "a": {
+      "description": "Alpha component (0-1)",
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "b": {
+      "description": "Blue component (0-1)",
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "g": {
+      "description": "Green component (0-1)",
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "r": {
+      "description": "Red component (0-1)",
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    }
+  },
+  "required": [
+    "r",
+    "g",
+    "b"
+  ],
+  "type": "object"
+}

addedInput schema / properties / height

Added value: +{
+  "description": "Height of the frame",
+  "type": "number"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Optional name for the frame",
+  "type": "string"
+}

addedInput schema / properties / parentId

Added value: +{
+  "description": "Optional parent node ID to append the frame to",
+  "type": "string"
+}

addedInput schema / properties / strokeColor

Added value: +{
+  "description": "Stroke color in RGBA format",
+  "properties": {
+    "a": {
+      "description": "Alpha component (0-1)",
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "b": {
+      "description": "Blue component (0-1)",
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "g": {
+      "description": "Green component (0-1)",
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "r": {
+      "description": "Red component (0-1)",
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    }
+  },
+  "required": [
+    "r",
+    "g",
+    "b"
+  ],
+  "type": "object"
+}

addedInput schema / properties / strokeWeight

Added value: +{
+  "description": "Stroke weight",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

addedInput schema / properties / width

Added value: +{
+  "description": "Width of the frame",
+  "type": "number"
+}

addedInput schema / properties / x

Added value: +{
+  "description": "X position",
+  "type": "number"
+}

addedInput schema / properties / y

Added value: +{
+  "description": "Y position",
+  "type": "number"
+}

addedInput schema / required

Added value: +[
+  "x",
+  "y",
+  "width",
+  "height"
+]

First observedAug 15, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure but only states 'Create a new frame.' It does not mention side effects, authentication needs, return values, or potential limitations. The schema hints at required fields, but that's not sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single-sentence description is concise and front-loaded, but given the tool's complexity (9 parameters, nested objects), slightly more detail could be beneficial without losing conciseness.

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?

For a tool with no annotations and no output schema, the description is too sparse. It does not explain what the tool returns, how to use it in a workflow, or any constraints beyond the schema. The schema helps, but the description should provide more context.

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 description coverage is 100%, providing detailed parameter descriptions (e.g., coordinate system, parent ID requirement). The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 'Create a new frame in Figma' clearly states the verb and resource, distinguishing it from sibling tools like create_rectangle or create_ellipse. However, it lacks specificity about the frame's role as a container or its relationship to other elements.

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 (e.g., create_rectangle, create_section). The schema contains a note about parentId being required, but the description itself offers no usage context or prerequisites.

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

Deploy Server