Skip to main content
Glama
yhc984

Talk to Figma MCP

by yhc984

create_rectangle

Add a rectangle to Figma designs by specifying position and dimensions. This tool enables programmatic shape creation through the Talk to Figma MCP server.

Instructions

Create a new rectangle in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX position
yYesY position
widthYesWidth of the rectangle
heightYesHeight of the rectangle
nameNoOptional name for the rectangle
parentIdNoOptional parent node ID to append the rectangle to

Implementation Reference

  • Core handler function that creates a rectangle in Figma using figma.createRectangle(), sets its position, dimensions, name, and appends it to a specified parent node or the current page.
    async function createRectangle(params) {
      const {
        x = 0,
        y = 0,
        width = 100,
        height = 100,
        name = "Rectangle",
        parentId,
      } = params || {};
    
      const rect = figma.createRectangle();
      rect.x = x;
      rect.y = y;
      rect.resize(width, height);
      rect.name = name;
    
      // If parentId is provided, append to that node, otherwise append to current page
      if (parentId) {
        const parentNode = await figma.getNodeByIdAsync(parentId);
        if (!parentNode) {
          throw new Error(`Parent node not found with ID: ${parentId}`);
        }
        if (!("appendChild" in parentNode)) {
          throw new Error(`Parent node does not support children: ${parentId}`);
        }
        parentNode.appendChild(rect);
      } else {
        figma.currentPage.appendChild(rect);
      }
    
      return {
        id: rect.id,
        name: rect.name,
        x: rect.x,
        y: rect.y,
        width: rect.width,
        height: rect.height,
        parentId: rect.parent ? rect.parent.id : undefined,
      };
    }
  • MCP tool registration for 'create_rectangle', including schema definition with Zod and proxy handler that forwards to Figma plugin via sendCommandToFigma.
    server.tool(
      "create_rectangle",
      "Create a new rectangle in Figma",
      {
        x: z.number().describe("X position"),
        y: z.number().describe("Y position"),
        width: z.number().describe("Width of the rectangle"),
        height: z.number().describe("Height of the rectangle"),
        name: z.string().optional().describe("Optional name for the rectangle"),
        parentId: z.string().optional().describe("Optional parent node ID to append the rectangle to")
      },
      async ({ x, y, width, height, name, parentId }) => {
        try {
          const result = await sendCommandToFigma('create_rectangle', {
            x, y, width, height, name: name || 'Rectangle', parentId
          });
          return {
            content: [
              {
                type: "text",
                text: `Created rectangle "${JSON.stringify(result)}"`
              }
            ]
          }
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error creating rectangle: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Registration/dispatch of 'create_rectangle' command in the Figma plugin's handleCommand switch statement.
    case "create_rectangle":
      return await createRectangle(params);
  • Input schema for create_rectangle tool using Zod validation.
      x: z.number().describe("X position"),
      y: z.number().describe("Y position"),
      width: z.number().describe("Width of the rectangle"),
      height: z.number().describe("Height of the rectangle"),
      name: z.string().optional().describe("Optional name for the rectangle"),
      parentId: z.string().optional().describe("Optional parent node ID to append the rectangle to")
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Create a new rectangle' implies a write/mutation operation, but the description doesn't disclose important behavioral traits like: whether this requires specific permissions, what happens if parentId is invalid, whether the rectangle becomes part of the current selection, or what the tool returns (though no output schema exists). For a mutation tool with zero annotation coverage, this is inadequate.

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 extremely concise at just 5 words, front-loading the essential information with zero waste. Every word earns its place, making it easy for an AI agent to parse quickly while understanding the core purpose.

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 mutation tool with 6 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address behavioral aspects, usage context, return values, or error conditions. While concise, it fails to provide the contextual information needed for an AI agent to use this tool effectively in the broader Figma tool ecosystem.

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%, so all parameters are documented in the schema. The description adds no parameter-specific information beyond what's already in the schema. The baseline score of 3 is appropriate when the schema does all the parameter documentation work, even though the description doesn't add any value in this area.

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 a new rectangle') and the resource ('in Figma'), providing specific verb+resource information. However, it doesn't differentiate this tool from similar sibling tools like 'create_frame' or 'create_component_instance' which also create visual elements in Figma, so it doesn't fully distinguish from alternatives.

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. There are multiple sibling tools for creating visual elements (create_frame, create_component_instance, create_text), but the description doesn't indicate when a rectangle is preferred over other shapes or elements, nor does it mention any prerequisites or constraints.

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/yhc984/cursor-talk-to-figma-mcp-main'

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