Skip to main content
Glama
yhc984

Talk to Figma MCP

by yhc984

set_fill_color

Change the fill color of Figma design elements like text or frames by specifying RGB(A) values to customize visual appearance.

Instructions

Set the fill color of a node in Figma can be TextNode or FrameNode

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to modify
rYesRed component (0-1)
gYesGreen component (0-1)
bYesBlue component (0-1)
aNoAlpha component (0-1)

Implementation Reference

  • Core handler function in the Figma plugin that retrieves the specified node by ID and sets its fill color using a solid Paint style constructed from RGBA parameters.
    async function setFillColor(params) {
      console.log("setFillColor", params);
      const {
        nodeId,
        color: { r, g, b, a },
      } = params || {};
    
      if (!nodeId) {
        throw new Error("Missing nodeId parameter");
      }
    
      const node = await figma.getNodeByIdAsync(nodeId);
      if (!node) {
        throw new Error(`Node not found with ID: ${nodeId}`);
      }
    
      if (!("fills" in node)) {
        throw new Error(`Node does not support fills: ${nodeId}`);
      }
    
      // Create RGBA color
      const rgbColor = {
        r: parseFloat(r) || 0,
        g: parseFloat(g) || 0,
        b: parseFloat(b) || 0,
        a: parseFloat(a) || 1,
      };
    
      // Set fill
      const paintStyle = {
        type: "SOLID",
        color: {
          r: parseFloat(rgbColor.r),
          g: parseFloat(rgbColor.g),
          b: parseFloat(rgbColor.b),
        },
        opacity: parseFloat(rgbColor.a),
      };
    
      console.log("paintStyle", paintStyle);
    
      node.fills = [paintStyle];
    
      return {
        id: node.id,
        name: node.name,
        fills: [paintStyle],
      };
    }
  • MCP server tool registration for 'set_fill_color', including input schema validation with Zod and a handler that proxies the command to the Figma plugin via WebSocket, returning a formatted response.
    server.tool(
      "set_fill_color",
      "Set the fill color of a node in Figma can be TextNode or FrameNode",
      {
        nodeId: z.string().describe("The ID of the node to modify"),
        r: z.number().min(0).max(1).describe("Red component (0-1)"),
        g: z.number().min(0).max(1).describe("Green component (0-1)"),
        b: z.number().min(0).max(1).describe("Blue component (0-1)"),
        a: z.number().min(0).max(1).optional().describe("Alpha component (0-1)")
      },
      async ({ nodeId, r, g, b, a }) => {
        try {
          const result = await sendCommandToFigma('set_fill_color', {
            nodeId,
            color: { r, g, b, a: a || 1 }
          });
          const typedResult = result as { name: string };
          return {
            content: [
              {
                type: "text",
                text: `Set fill color of node "${typedResult.name}" to RGBA(${r}, ${g}, ${b}, ${a || 1})`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting fill color: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Dispatch case in the Figma plugin's handleCommand function that routes 'set_fill_color' commands to the setFillColor handler.
    case "set_fill_color":
      return await setFillColor(params);
  • Zod schema definition for the input parameters of the set_fill_color MCP tool.
    {
      nodeId: z.string().describe("The ID of the node to modify"),
      r: z.number().min(0).max(1).describe("Red component (0-1)"),
      g: z.number().min(0).max(1).describe("Green component (0-1)"),
      b: z.number().min(0).max(1).describe("Blue component (0-1)"),
      a: z.number().min(0).max(1).optional().describe("Alpha component (0-1)")
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but provides minimal behavioral context. It states the tool modifies nodes but doesn't disclose whether this is a destructive/mutative operation (implied by 'Set'), what permissions are needed, whether changes are reversible, error conditions, or what happens if applied to incompatible nodes. For a mutation tool with zero annotation coverage, this is inadequate 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?

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a simple tool, though it could be slightly more structured by separating purpose from constraints. Every word earns its place, making it easy to parse quickly.

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 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what happens after setting the color (success response, error cases), doesn't mention the tool's effect on the design (immediate visual change?), and provides no context about Figma's color system or how this interacts with other properties. The description alone is insufficient for safe, effective use.

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 parameters are fully documented in the schema. The description adds no parameter-specific information beyond mentioning node types (TextNode/FrameNode), which relates to the 'nodeId' parameter but doesn't explain format or constraints. With complete schema coverage, baseline 3 is appropriate as the description provides minimal additional semantic value.

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 ('Set the fill color') and target resource ('a node in Figma'), specifying applicable node types ('TextNode or FrameNode'). It distinguishes from similar tools like 'set_stroke_color' by focusing on fill color, but doesn't explicitly differentiate from other color-related tools or explain why this tool exists versus general property-setting tools.

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. It doesn't mention prerequisites (e.g., needing nodeId from selection or other tools), doesn't specify when fill color applies versus other color properties, and provides no comparison to sibling tools like 'set_stroke_color' or general modification tools. The description only states what it does, not when to choose it.

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