Skip to main content
Glama

set_stroke_color

Modify stroke color and weight for design elements in Figma by specifying RGB values and optional opacity settings.

Instructions

Set the stroke color of a node in Figma (defaults: opacity 1, weight 1)

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)
strokeWeightNoStroke weight >= 0)

Implementation Reference

  • The handler function that implements the core logic for the 'set_stroke_color' tool. It validates required RGB components, applies defaults for alpha and stroke weight using utility functions, sends the formatted command to Figma over websocket, and returns a structured text response with the node's name or error message.
    async ({ nodeId, r, g, b, a, strokeWeight }) => {
      try {
    
        if (r === undefined || g === undefined || b === undefined) {
          throw new Error("RGB components (r, g, b) are required and cannot be undefined");
        }
        
        const colorInput: Color = { r, g, b, a };
        const colorWithDefaults = applyColorDefaults(colorInput);
        
        const strokeWeightWithDefault = applyDefault(strokeWeight, FIGMA_DEFAULTS.stroke.weight);
        
        const result = await sendCommandToFigma("set_stroke_color", {
          nodeId,
          color: colorWithDefaults,
          strokeWeight: strokeWeightWithDefault,
        });
        const typedResult = result as { name: string };
        return {
          content: [
            {
              type: "text",
              text: `Set stroke color of node "${typedResult.name}" to RGBA(${r}, ${g}, ${b}, ${colorWithDefaults.a}) with weight ${strokeWeightWithDefault}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error setting stroke color: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
        };
      }
    }
  • Zod schema defining the input parameters for the 'set_stroke_color' tool, including required nodeId and RGB values (0-1 range), optional alpha and strokeWeight with validation.
    {
      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)"),
      strokeWeight: z.number().min(0).optional().describe("Stroke weight >= 0)"),
    },
  • The complete registration of the 'set_stroke_color' MCP tool using server.tool(), including tool name, description, input schema, and inline handler function. This is called within registerModificationTools which is invoked from the tools index.
    server.tool(
      "set_stroke_color",
      "Set the stroke color of a node in Figma (defaults: opacity 1, weight 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)"),
        strokeWeight: z.number().min(0).optional().describe("Stroke weight >= 0)"),
      },
      async ({ nodeId, r, g, b, a, strokeWeight }) => {
        try {
    
          if (r === undefined || g === undefined || b === undefined) {
            throw new Error("RGB components (r, g, b) are required and cannot be undefined");
          }
          
          const colorInput: Color = { r, g, b, a };
          const colorWithDefaults = applyColorDefaults(colorInput);
          
          const strokeWeightWithDefault = applyDefault(strokeWeight, FIGMA_DEFAULTS.stroke.weight);
          
          const result = await sendCommandToFigma("set_stroke_color", {
            nodeId,
            color: colorWithDefaults,
            strokeWeight: strokeWeightWithDefault,
          });
          const typedResult = result as { name: string };
          return {
            content: [
              {
                type: "text",
                text: `Set stroke color of node "${typedResult.name}" to RGBA(${r}, ${g}, ${b}, ${colorWithDefaults.a}) with weight ${strokeWeightWithDefault}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting stroke color: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
          };
        }
      }
    );

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
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 mentions default values (opacity 1, weight 1), which is useful context beyond the schema. However, it doesn't disclose critical behavioral traits: whether this is a mutation (implied but not stated), what permissions are needed, if changes are reversible, error conditions (e.g., invalid nodeId), or response format. 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.

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the core purpose and includes helpful default information. Every word earns its place—no redundancy or fluff. It's appropriately sized for a straightforward tool with well-documented parameters.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (success/failure, updated node object, etc.), error handling, or side effects. While parameters are well-covered by the schema, the behavioral context is lacking for safe and effective use by an AI agent.

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 already documents all 6 parameters thoroughly. The description adds minimal value by implying defaults for 'a' (opacity) and 'strokeWeight', but doesn't explain parameter interactions or semantics beyond what's in the schema (e.g., that r/g/b are required while a/strokeWeight are optional with defaults). Baseline 3 is appropriate when schema does the heavy lifting.

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 stroke color') and target resource ('of a node in Figma'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'set_fill_color' by focusing specifically on stroke color. However, it doesn't explicitly differentiate from other stroke-related tools that might exist (though none are listed among siblings), keeping it from a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., node must exist, must support strokes), compare with similar tools like 'set_effects' or 'set_effect_style_id', or specify when not to use it (e.g., for fill color). The agent must infer usage solely from the tool name and parameters.

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