Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk

create_sticky

Create a sticky note in a FigJam board to add text content at a specified position. Customize with background color and wide format.

Instructions

Create a sticky note in a FigJam board. Sticky notes are the primary way to add text content in FigJam.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX position on the canvas
yYesY position on the canvas
textYesText content of the sticky note
colorNoBackground color of the sticky note (default: yellow). Supported values: yellow, pink, green, blue, purple, red, orange, teal, gray, white.
isWideNoWhether the sticky note should be wide format (default: false)
nameNoOptional name/label for the node
parentIdNoParent node ID. REQUIRED — server enforces this. Use page node ID for top-level elements. Get page IDs via get_pages tool.

Implementation Reference

  • MCP tool handler for 'create_sticky'. Registers the tool with Zod schema validation for x, y, text, color, isWide, name, and parentId. Sends command to Figma via WebSocket.
    server.tool(
      "create_sticky",
      "Create a sticky note in a FigJam board. Sticky notes are the primary way to add text content in FigJam.",
      {
        x: z.number().describe("X position on the canvas"),
        y: z.number().describe("Y position on the canvas"),
        text: z.string().describe("Text content of the sticky note"),
        color: z
          .enum([
            "yellow",
            "pink",
            "green",
            "blue",
            "purple",
            "red",
            "orange",
            "teal",
            "gray",
            "white",
          ])
          .optional()
          .describe(
            "Background color of the sticky note (default: yellow). Supported values: yellow, pink, green, blue, purple, red, orange, teal, gray, white."
          ),
        isWide: z
          .boolean()
          .optional()
          .describe("Whether the sticky note should be wide format (default: false)"),
        name: z.string().optional().describe("Optional name/label for the node"),
        parentId: z
          .string()
          .optional()
          .describe("Parent node ID. REQUIRED — server enforces this. Use page node ID for top-level elements. Get page IDs via get_pages tool."),
      },
      async ({ x, y, text, color, isWide, name, parentId }) => {
        try {
          const result = await sendCommandToFigma("create_sticky", {
            x,
            y,
            text,
            color: color ?? "yellow",
            isWide: isWide ?? false,
            name,
            parentId,
          });
          return {
            content: [
              {
                type: "text",
                text: `Created sticky note: ${JSON.stringify(result)}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error creating sticky note: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
          };
        }
      }
    );
  • TypeScript type definition including 'create_sticky' as a valid FigmaCommand in the union type.
    | "create_sticky"
    | "set_sticky_text"
    | "create_shape_with_text"
    | "create_connector"
    | "create_section";
  • Tool registration via server.tool() call in registerFigJamTools function. The function is called from src/talk_to_figma_mcp/tools/index.ts:27.
    server.tool(
      "create_sticky",
      "Create a sticky note in a FigJam board. Sticky notes are the primary way to add text content in FigJam.",
      {
        x: z.number().describe("X position on the canvas"),
        y: z.number().describe("Y position on the canvas"),
        text: z.string().describe("Text content of the sticky note"),
        color: z
          .enum([
            "yellow",
            "pink",
            "green",
            "blue",
            "purple",
            "red",
            "orange",
            "teal",
            "gray",
            "white",
          ])
          .optional()
          .describe(
            "Background color of the sticky note (default: yellow). Supported values: yellow, pink, green, blue, purple, red, orange, teal, gray, white."
          ),
        isWide: z
          .boolean()
          .optional()
          .describe("Whether the sticky note should be wide format (default: false)"),
        name: z.string().optional().describe("Optional name/label for the node"),
        parentId: z
          .string()
          .optional()
          .describe("Parent node ID. REQUIRED — server enforces this. Use page node ID for top-level elements. Get page IDs via get_pages tool."),
      },
      async ({ x, y, text, color, isWide, name, parentId }) => {
        try {
          const result = await sendCommandToFigma("create_sticky", {
            x,
            y,
            text,
            color: color ?? "yellow",
            isWide: isWide ?? false,
            name,
            parentId,
          });
          return {
            content: [
              {
                type: "text",
                text: `Created sticky note: ${JSON.stringify(result)}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error creating sticky note: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
          };
        }
      }
    );
  • Listed in CREATION_COMMANDS set on the server-side socket relay, enforcing that a parentId parameter is required for all creation commands.
      "create_section", "create_sticky", "create_shape_with_text", "create_connector",
    ]);
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states creation and primary use for text. Critical details like the required parentId (enforced server-side) are not mentioned, nor any mutation implications or side effects.

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?

Two sentences, front-loaded with the core action and context. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given thorough schema descriptions and no output schema, the description covers basic purpose but lacks mention of important constraints (e.g., parentId requirement) that are only in the property descriptions. It could provide more integration context with sibling tools.

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 descriptions for all parameters. The main description adds no additional semantic meaning beyond the schema, so baseline 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 clearly states 'Create a sticky note in a FigJam board' and notes that sticky notes are the primary way to add text content. However, it does not differentiate from sibling tools like create_text or create_shape_with_text, which also add text.

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 explicit guidance on when to use this tool versus alternatives. The description implies sticky notes are primary for text, but does not specify exclusions or provide when-not-to-use advice.

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