Skip to main content
Glama
yhc984

Talk to Figma MCP

by yhc984

set_corner_radius

Modify corner radius values for Figma design elements. Specify which corners to round and apply precise radius measurements to nodes.

Instructions

Set the corner radius of a node in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to modify
radiusYesCorner radius value
cornersNoOptional array of 4 booleans to specify which corners to round [topLeft, topRight, bottomRight, bottomLeft]

Implementation Reference

  • Core handler function that executes the set corner radius logic on Figma nodes, supporting both uniform and individual corner radii.
    async function setCornerRadius(params) {
      const { nodeId, radius, corners } = params || {};
    
      if (!nodeId) {
        throw new Error("Missing nodeId parameter");
      }
    
      if (radius === undefined) {
        throw new Error("Missing radius parameter");
      }
    
      const node = await figma.getNodeByIdAsync(nodeId);
      if (!node) {
        throw new Error(`Node not found with ID: ${nodeId}`);
      }
    
      // Check if node supports corner radius
      if (!("cornerRadius" in node)) {
        throw new Error(`Node does not support corner radius: ${nodeId}`);
      }
    
      // If corners array is provided, set individual corner radii
      if (corners && Array.isArray(corners) && corners.length === 4) {
        if ("topLeftRadius" in node) {
          // Node supports individual corner radii
          if (corners[0]) node.topLeftRadius = radius;
          if (corners[1]) node.topRightRadius = radius;
          if (corners[2]) node.bottomRightRadius = radius;
          if (corners[3]) node.bottomLeftRadius = radius;
        } else {
          // Node only supports uniform corner radius
          node.cornerRadius = radius;
        }
      } else {
        // Set uniform corner radius
        node.cornerRadius = radius;
      }
    
      return {
        id: node.id,
        name: node.name,
        cornerRadius: "cornerRadius" in node ? node.cornerRadius : undefined,
        topLeftRadius: "topLeftRadius" in node ? node.topLeftRadius : undefined,
        topRightRadius: "topRightRadius" in node ? node.topRightRadius : undefined,
        bottomRightRadius:
          "bottomRightRadius" in node ? node.bottomRightRadius : undefined,
        bottomLeftRadius:
          "bottomLeftRadius" in node ? node.bottomLeftRadius : undefined,
      };
    }
  • Dispatch/registration of the set_corner_radius command in the Figma plugin's main command handler.
    case "set_corner_radius":
      return await setCornerRadius(params);
  • MCP tool registration for set_corner_radius, including the thin wrapper handler that proxies to Figma plugin.
    server.tool(
      "set_corner_radius",
      "Set the corner radius of a node in Figma",
      {
        nodeId: z.string().describe("The ID of the node to modify"),
        radius: z.number().min(0).describe("Corner radius value"),
        corners: z.array(z.boolean()).length(4).optional().describe("Optional array of 4 booleans to specify which corners to round [topLeft, topRight, bottomRight, bottomLeft]")
      },
      async ({ nodeId, radius, corners }) => {
        try {
          const result = await sendCommandToFigma('set_corner_radius', {
            nodeId,
            radius,
            corners: corners || [true, true, true, true]
          });
          const typedResult = result as { name: string };
          return {
            content: [
              {
                type: "text",
                text: `Set corner radius of node "${typedResult.name}" to ${radius}px`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting corner radius: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Input schema validation using Zod for the set_corner_radius tool parameters.
    {
      nodeId: z.string().describe("The ID of the node to modify"),
      radius: z.number().min(0).describe("Corner radius value"),
      corners: z.array(z.boolean()).length(4).optional().describe("Optional array of 4 booleans to specify which corners to round [topLeft, topRight, bottomRight, bottomLeft]")
    },
  • TypeScript type definition including set_corner_radius in FigmaCommand union.
    | 'set_corner_radius';
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool modifies a node, implying mutation, but doesn't clarify whether this requires specific permissions, if changes are reversible, what happens to existing corner settings, or potential side effects (e.g., visual updates). For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 without unnecessary words. Every part of the sentence ('Set the corner radius of a node in Figma') directly contributes to understanding the tool's function, with zero waste or redundancy.

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 address behavioral aspects like error conditions, permissions, or what the tool returns (e.g., success confirmation or updated node data). Given the complexity of modifying Figma nodes and the lack of structured safety hints, more context is needed for reliable agent 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%, with all parameters clearly documented in the schema (nodeId, radius, corners). The description adds no additional parameter semantics beyond what's already in the schema—it doesn't explain units for 'radius', typical values, or practical examples for the 'corners' array. Baseline 3 is appropriate when the 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') and resource ('corner radius of a node in Figma'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'set_fill_color' or 'set_stroke_color' by specifying the exact property being modified. However, it doesn't explicitly differentiate from other geometry-modifying tools like 'resize_node' beyond the property name.

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., needing a valid node ID), exclusions (e.g., nodes that don't support corner radius), or related tools (e.g., 'set_layout_mode' for other geometry adjustments). The agent must infer usage from the tool name and parameters alone.

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