Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk

set_variable

Create or update a variable in a Figma design system by specifying its name, type (color, float, string, boolean), and value. Optionally create a new variable collection if provided collection name doesn't exist.

Instructions

Create or update a variable in a Figma variable collection. Creates the collection if collectionName is provided and it doesn't exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionIdNoID of an existing variable collection
collectionNameNoName for a new collection (used if collectionId not provided)
nameYesVariable name
resolvedTypeYesVariable type
valueNoVariable value. COLOR: {r,g,b,a} (0-1). FLOAT: number. STRING: string. BOOLEAN: boolean.
modeIdNoMode ID to set the value for (uses default mode if omitted)

Implementation Reference

  • The handler for the 'set_variable' tool. Registers the tool on the MCP server with Zod schema for inputs (collectionId, collectionName, name, resolvedType, value, modeId) and sends the command via WebSocket to Figma.
    // Set Variable Tool
    server.tool(
      "set_variable",
      "Create or update a variable in a Figma variable collection. Creates the collection if collectionName is provided and it doesn't exist.",
      {
        collectionId: z.string().optional().describe("ID of an existing variable collection"),
        collectionName: z.string().optional().describe("Name for a new collection (used if collectionId not provided)"),
        name: z.string().describe("Variable name"),
        resolvedType: z.enum(["COLOR", "FLOAT", "STRING", "BOOLEAN"]).describe("Variable type"),
        value: z.any().describe("Variable value. COLOR: {r,g,b,a} (0-1). FLOAT: number. STRING: string. BOOLEAN: boolean."),
        modeId: z.string().optional().describe("Mode ID to set the value for (uses default mode if omitted)"),
      },
      async ({ collectionId, collectionName, name, resolvedType, value, modeId }) => {
        try {
          const result = await sendCommandToFigma("set_variable", {
            collectionId,
            collectionName,
            name,
            resolvedType,
            value,
            modeId,
          });
          const typedResult = result as { variableId: string; variableName: string; collectionName: string };
          return {
            content: [
              {
                type: "text",
                text: `Set variable "${typedResult.variableName}" in collection "${typedResult.collectionName}" (ID: ${typedResult.variableId})`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting variable: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
          };
        }
      }
    );
  • Zod schema definition for the 'set_variable' tool inputs: collectionId (optional), collectionName (optional), name (required), resolvedType (enum: COLOR/FLOAT/STRING/BOOLEAN), value (any), modeId (optional).
    {
      collectionId: z.string().optional().describe("ID of an existing variable collection"),
      collectionName: z.string().optional().describe("Name for a new collection (used if collectionId not provided)"),
      name: z.string().describe("Variable name"),
      resolvedType: z.enum(["COLOR", "FLOAT", "STRING", "BOOLEAN"]).describe("Variable type"),
      value: z.any().describe("Variable value. COLOR: {r,g,b,a} (0-1). FLOAT: number. STRING: string. BOOLEAN: boolean."),
      modeId: z.string().optional().describe("Mode ID to set the value for (uses default mode if omitted)"),
  • Registration of the 'set_variable' tool via server.tool() inside registerVariableTools(server), which is called from registerTools(server) in server.ts.
    // Set Variable Tool
    server.tool(
      "set_variable",
      "Create or update a variable in a Figma variable collection. Creates the collection if collectionName is provided and it doesn't exist.",
      {
        collectionId: z.string().optional().describe("ID of an existing variable collection"),
        collectionName: z.string().optional().describe("Name for a new collection (used if collectionId not provided)"),
        name: z.string().describe("Variable name"),
        resolvedType: z.enum(["COLOR", "FLOAT", "STRING", "BOOLEAN"]).describe("Variable type"),
        value: z.any().describe("Variable value. COLOR: {r,g,b,a} (0-1). FLOAT: number. STRING: string. BOOLEAN: boolean."),
        modeId: z.string().optional().describe("Mode ID to set the value for (uses default mode if omitted)"),
      },
      async ({ collectionId, collectionName, name, resolvedType, value, modeId }) => {
        try {
          const result = await sendCommandToFigma("set_variable", {
            collectionId,
            collectionName,
            name,
            resolvedType,
            value,
            modeId,
          });
          const typedResult = result as { variableId: string; variableName: string; collectionName: string };
          return {
            content: [
              {
                type: "text",
                text: `Set variable "${typedResult.variableName}" in collection "${typedResult.collectionName}" (ID: ${typedResult.variableId})`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting variable: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
          };
        }
      }
    );
  • Type definition: 'set_variable' is included as a valid value in the FigmaCommand union type, ensuring type safety for commands sent via WebSocket.
    | "set_variable"
  • The sendCommandToFigma helper function used by the set_variable handler to send the command string 'set_variable' via WebSocket 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));
      });
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. Removed
  2. Added
  3. Removed
  4. Addedv0.8.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It explains the collection creation behavior but does not mention whether updates overwrite or merge, required permissions, error conditions, or what happens if collectionId refers to a non-existent collection. Adequate but not comprehensive.

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 two sentences, no filler, front-loaded with the purpose. Every sentence adds value.

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 6 parameters, no output schema, and no annotations, the description covers core behavior but lacks details on error handling, return values, default mode behavior, and invalid value handling. Adequate for a simple tool but incomplete.

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%, so baseline is 3. The description adds minor context about the interaction between collectionId and collectionName but does not provide additional semantics beyond the schema descriptions.

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 tool creates or updates a variable in a Figma variable collection, and explicitly mentions that it creates the collection if collectionName is provided and doesn't exist. This distinguishes it from sibling tools like get_variables (read) and apply_variable_to_node (apply).

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 (e.g., switch_variable_mode). The description implies usage for creating or updating variables but does not provide context on when not to use it or what prerequisites are needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools