Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

create_star

Creates a star shape in Figma at specified coordinates, with customizable width, height, number of points, inner radius, fill color, stroke, and optional name. Requires parent node ID.

Instructions

Create a new star in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX position (local coordinates, relative to parent)
yYesY position (local coordinates, relative to parent)
widthYesWidth of the star
heightYesHeight of the star
pointsNoNumber of points (default: 5)
innerRadiusNoInner radius ratio (0.01-0.99, default: 0.5)
nameNoOptional name for the star
parentIdNoParent node ID. REQUIRED — server enforces this. Use page node ID for top-level elements. Get page IDs via get_pages tool.
fillColorNoFill color in RGBA format
strokeColorNoStroke color in RGBA format
strokeWeightNoStroke weight

Schema Changelog

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

  1. Changed6 schema fields changedv0.8.2
    • 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 star 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)"
  2. Changed13 schema fields changedv1.0.0
    • 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 star",
+  "type": "number"
+}
    • addedInput schema / properties / innerRadius
      Added value: +{
+  "description": "Inner radius ratio (0.01-0.99, default: 0.5)",
+  "maximum": 0.99,
+  "minimum": 0.01,
+  "type": "number"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Optional name for the star",
+  "type": "string"
+}
    • addedInput schema / properties / parentId
      Added value: +{
+  "description": "Optional parent node ID to append the star to",
+  "type": "string"
+}
    • addedInput schema / properties / points
      Added value: +{
+  "description": "Number of points (default: 5)",
+  "minimum": 3,
+  "type": "number"
+}
    • 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 star",
+  "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"
+]
  3. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries full responsibility. It fails to disclose side effects, required permissions, return value, or whether the operation is reversible, leaving significant gaps.

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 sentence, concise and to the point. However, it could include more context without becoming verbose, so it earns a 4 rather than 5.

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 11 parameters, nested objects, and no output schema, the description is too sparse. It does not explain return behavior, restrictions, or lifecycle implications, making it incomplete for an autonomous agent.

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% with good descriptions. The description adds value for parentId by clarifying it is required and suggesting get_pages for page IDs, but overall adds little beyond 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?

The description clearly states the verb ('Create') and resource ('a new star in Figma'), distinguishing it from sibling tools like create_rectangle or create_ellipse.

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?

No explicit when-to-use or when-not-to-use guidance is given. The description provides a hint about parentId requirements, but does not address selection among similar shape-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/arinspunk/claude-talk-to-figma-mcp'

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