Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

create_text

Add text to Figma designs at defined coordinates, with control over font size, weight, color, alignment, and auto-resize settings.

Instructions

Create a new text element in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX position (local coordinates, relative to parent)
yYesY position (local coordinates, relative to parent)
textYesText content
fontSizeNoFont size (default: 14)
fontWeightNoFont weight (e.g., 400 for Regular, 700 for Bold)
fontColorNoFont color in RGBA format
nameNoOptional name for the text node by default following text
parentIdNoParent node ID. REQUIRED — server enforces this. Use page node ID for top-level elements. Get page IDs via get_pages tool.
textAlignHorizontalNoHorizontal text alignment. Use RIGHT for Arabic/RTL text.
textAutoResizeNoText resize behavior. Use HEIGHT for fixed-width text that wraps.
widthNoFixed width for the text node. Use with textAutoResize HEIGHT for wrapping text within a specific width.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changedv0.8.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / fontColor / additionalProperties
      Added value: +false
    • changedInput schema / properties / parentId / description
      Previous value: -"Optional parent node ID to append the text 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 / textAlignHorizontal
      Added value: +{
+  "description": "Horizontal text alignment. Use RIGHT for Arabic/RTL text.",
+  "enum": [
+    "LEFT",
+    "CENTER",
+    "RIGHT",
+    "JUSTIFIED"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / textAutoResize
      Added value: +{
+  "description": "Text resize behavior. Use HEIGHT for fixed-width text that wraps.",
+  "enum": [
+    "WIDTH_AND_HEIGHT",
+    "HEIGHT",
+    "NONE",
+    "TRUNCATE"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / width
      Added value: +{
+  "description": "Fixed width for the text node. Use with textAutoResize HEIGHT for wrapping text within a specific width.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
    • 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)"
  2. Changed10 schema fields changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / fontColor
      Added value: +{
+  "description": "Font 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 / fontSize
      Added value: +{
+  "description": "Font size (default: 14)",
+  "type": "number"
+}
    • addedInput schema / properties / fontWeight
      Added value: +{
+  "description": "Font weight (e.g., 400 for Regular, 700 for Bold)",
+  "type": "number"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Optional name for the text node by default following text",
+  "type": "string"
+}
    • addedInput schema / properties / parentId
      Added value: +{
+  "description": "Optional parent node ID to append the text to",
+  "type": "string"
+}
    • addedInput schema / properties / text
      Added value: +{
+  "description": "Text content",
+  "type": "string"
+}
    • 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",
+  "text"
+]
  3. First observed

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 should carry behavioral context. It only states the basic action, omitting important details like side effects, requirements (e.g., parentId), or the need to load fonts first.

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 description is a single concise sentence. It could benefit from slightly more structure (e.g., a brief list of required inputs), but it is not verbose.

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 (11 parameters, no output schema or annotations), the description is insufficient. It fails to mention critical context like the required parentId or the need to use load_font_async first.

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 parameter meaning beyond the schema descriptions, which are already detailed.

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 action (create) and resource (text element) in Figma. It is specific and directly conveys the tool's function, though it does not differentiate from sibling create tools.

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?

The description provides no guidance on when to use this tool versus alternatives like create_shape_with_text or other create tools. It lacks any context about prerequisites or typical usage scenarios.

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/arinspunk/claude-talk-to-figma-mcp'

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