Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk

set_sticky_text

Update the text content of an existing FigJam sticky note by specifying its node ID and the new text.

Instructions

Update the text content of an existing FigJam sticky note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the sticky note node to update
textYesThe new text content

Implementation Reference

  • The tool registration and handler for 'set_sticky_text'. Accepts nodeId and text, sends command via WebSocket to Figma.
    server.tool(
      "set_sticky_text",
      "Update the text content of an existing FigJam sticky note.",
      {
        nodeId: z.string().describe("The ID of the sticky note node to update"),
        text: z.string().describe("The new text content"),
      },
      async ({ nodeId, text }) => {
        try {
          const result = await sendCommandToFigma("set_sticky_text", {
            nodeId,
            text,
          });
          return {
            content: [
              {
                type: "text",
                text: `Updated sticky note text: ${JSON.stringify(result)}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error updating sticky note text: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
          };
        }
      }
    );
  • Type definition: 'set_sticky_text' is included as a valid FigmaCommand in the FigmaCommand union type.
    | "set_sticky_text"
    | "create_shape_with_text"
    | "create_connector"
    | "create_section";
  • Registration of the tool on the MCP server via server.tool() within registerFigJamTools().
    server.tool(
      "set_sticky_text",
      "Update the text content of an existing FigJam sticky note.",
      {
        nodeId: z.string().describe("The ID of the sticky note node to update"),
        text: z.string().describe("The new text content"),
      },
      async ({ nodeId, text }) => {
        try {
          const result = await sendCommandToFigma("set_sticky_text", {
            nodeId,
            text,
          });
          return {
            content: [
              {
                type: "text",
                text: `Updated sticky note text: ${JSON.stringify(result)}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error updating sticky note text: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
          };
        }
      }
    );
  • Helper function that sends a command (including 'set_sticky_text') to the Figma server via WebSocket and returns a promise.
    export function sendCommandToFigma(
      command: FigmaCommand,
      params: unknown = {},
      timeoutMs: number = 300000
    ): Promise<unknown> {
      return new Promise((resolve, reject) => {
        // If not connected, try to connect first
        if (!ws || ws.readyState !== WebSocket.OPEN) {
          connectToFigma();
          reject(new Error("Not connected to Figma. Attempting to connect..."));
          return;
        }
    
        // Check if we need a channel for this command
        const requiresChannel = command !== "join";
        if (requiresChannel && !currentChannel) {
          reject(new Error("Must join a channel before sending commands"));
          return;
        }
    
        const id = uuidv4();
        const request = {
          id,
          type: command === "join" ? "join" : "message",
          ...(command === "join"
            ? { channel: (params as any).channel, sessionId: SESSION_ID }
            : { channel: currentChannel }),
          message: {
            id,
            command,
            params: {
              ...(params as any),
              commandId: id, // Include the command ID in params
            },
          },
        };
    
        // Set timeout for request
        const timeout = setTimeout(() => {
          if (pendingRequests.has(id)) {
            pendingRequests.delete(id);
            logger.error(`Request ${id} to Figma timed out after ${timeoutMs / 1000} seconds`);
            reject(new Error('Request to Figma timed out'));
          }
        }, timeoutMs);
    
        // Store the promise callbacks to resolve/reject later
        pendingRequests.set(id, {
          resolve,
          reject,
          timeout,
          lastActivity: Date.now()
        });
    
        // Send the request
        logger.info(`Sending command to Figma: ${command}`);
        logger.debug(`Request details: ${JSON.stringify(request)}`);
        ws.send(JSON.stringify(request));
      });
    }
Behavior2/5

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

No annotations provided, so description carries full burden. Only states 'update text content' without disclosing behavioral traits like whether it's destructive, permissions needed, error handling, or if text replaces or appends. Minimal transparency.

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?

Single sentence of 9 words is efficient and front-loaded. Could add brief usage context without losing conciseness, but overall well-structured.

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?

Simple tool with 2 params and no output schema. Description provides minimal context; lacks details on return value, side effects, or error conditions. Adequate for basic understanding but incomplete for full agent guidance.

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 clear parameter descriptions. The tool description adds no additional 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool updates text content of an existing FigJam sticky note, using specific verb and resource. Differentiates from siblings like 'create_sticky' and 'set_text_content' by specifying 'FigJam sticky note'.

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 on when to use this tool versus alternatives (e.g., create_sticky for new notes, set_text_content for Figma text). No mention of prerequisites, constraints, or when not to use.

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