Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk

set_text_decoration

Modify text decoration in Figma by setting underline, strikethrough, or none on a text node. Specify the node ID and choose the decoration type.

Instructions

Set the text decoration of a text node in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the text node to modify
textDecorationYesText decoration type

Implementation Reference

  • The set_text_decoration tool handler. It registers an MCP tool via server.tool() that accepts nodeId (string) and textDecoration (enum: NONE, UNDERLINE, STRIKETHROUGH), then sends the command to Figma via WebSocket.
    // Set Text Decoration Tool
    server.tool(
      "set_text_decoration",
      "Set the text decoration of a text node in Figma",
      {
        nodeId: z.string().describe("The ID of the text node to modify"),
        textDecoration: z.enum(["NONE", "UNDERLINE", "STRIKETHROUGH"]).describe("Text decoration type"),
      },
      async ({ nodeId, textDecoration }) => {
        try {
          const result = await sendCommandToFigma("set_text_decoration", {
            nodeId,
            textDecoration
          });
          const typedResult = result as { name: string, textDecoration: string };
          return {
            content: [
              {
                type: "text",
                text: `Updated text decoration of node "${typedResult.name}" to ${typedResult.textDecoration}`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting text decoration: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
  • The 'set_text_decoration' string literal is included in the FigmaCommand union type, defining it as a valid command type that can be passed to sendCommandToFigma.
    | "set_text_decoration"
  • The tool is registered via server.tool() within the registerTextTools function. This is both the handler and the registration point, as MCP tools are registered at the same time they are defined.
    // Set Text Decoration Tool
    server.tool(
      "set_text_decoration",
      "Set the text decoration of a text node in Figma",
      {
        nodeId: z.string().describe("The ID of the text node to modify"),
        textDecoration: z.enum(["NONE", "UNDERLINE", "STRIKETHROUGH"]).describe("Text decoration type"),
      },
      async ({ nodeId, textDecoration }) => {
        try {
          const result = await sendCommandToFigma("set_text_decoration", {
            nodeId,
            textDecoration
          });
          const typedResult = result as { name: string, textDecoration: string };
          return {
            content: [
              {
                type: "text",
                text: `Updated text decoration of node "${typedResult.name}" to ${typedResult.textDecoration}`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting text decoration: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • The sendCommandToFigma helper function that sends the 'set_text_decoration' command (and any other command) over a WebSocket connection to the Figma plugin server.
    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?

The description implies a write operation (mutation) but does not disclose potential side effects, required permissions, or error conditions. Since no annotations are provided, the description should cover behavioral traits, but it offers minimal insight beyond the verb.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but may be overly minimal. It avoids fluff but lacks sufficient detail for an agent to fully understand the tool's behavior, making it borderline adequate.

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 absence of annotations and output schema, the description should provide richer context about behavior, prerequisites, and return values. It fails to explain what happens when the decoration is set, how it interacts with other properties, or any limitations.

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?

The input schema already provides descriptions for both parameters (nodeId and textDecoration), achieving 100% coverage. The description adds no additional parameter meaning beyond what the schema conveys, so a baseline score of 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 the verb 'Set', the resource 'text decoration', and the context 'text node in Figma'. It is specific to a single property, but does not differentiate from sibling tools like 'set_text_style_id' which may also affect decoration.

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 is provided on when to use this tool versus alternatives, such as when to modify text decoration via styles vs directly. No usage constraints or prerequisites (e.g., font loading) are mentioned.

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