Skip to main content
Glama

set_fill_color

Change the fill color of Figma design elements like text or frames by specifying RGB values and node ID.

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

  • Registration of the 'set_fill_color' MCP tool. Includes the tool name, description, Zod input schema for nodeId and RGBA color components, and the handler function that sends the command to the Figma plugin and formats the 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)
                  }`,
              },
            ],
          };
        }
      }
    );
  • The handler function executes the tool logic by calling sendCommandToFigma with the set_fill_color command and the nodeId and color parameters. It formats a success message with the node name and RGBA values or an error message.
    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)
                }`,
            },
          ],
        };
      }
    }
  • Zod schema for input validation of the set_fill_color tool parameters: nodeId (string), r, g, b (numbers between 0 and 1), a (optional number between 0 and 1).
    {
      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 for behavioral disclosure. It states this is a modification operation ('Set'), implying mutation, but doesn't disclose permission requirements, whether changes are reversible, error conditions, or what happens if the node doesn't support fill colors. For a mutation tool with zero annotation coverage, this is insufficient.

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 communicates the core purpose without unnecessary words. It could be slightly improved by front-loading the most critical information more explicitly, but it's appropriately sized for its purpose.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what happens after setting the color, what the return value might be, error conditions, or constraints beyond node types. Given the complexity of modifying Figma nodes, more context is needed.

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 the schema fully documents all 5 parameters. The description doesn't add any parameter-specific information beyond what's in the schema, but with complete schema coverage, the 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 action ('Set the fill color') and target ('a node in Figma'), and specifies the node types ('TextNode or FrameNode'). It distinguishes from siblings like set_stroke_color by focusing on fill color, but doesn't explicitly contrast with other color-related 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 is provided on when to use this tool versus alternatives like set_stroke_color or other styling tools. The description mentions node types but doesn't explain when this operation is appropriate or what prerequisites might exist.

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/pipethedev/Talk-to-Figma-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server