Skip to main content
Glama
paragdesai1

Cursor Talk to Figma MCP

by paragdesai1

set_corner_radius

Adjust corner radius values for Figma design elements to create rounded edges or modify existing curvature.

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 using Figma API. Retrieves the node by ID, validates support for cornerRadius, and sets uniform radius or individual corner radii based on the 'corners' parameter.
    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,
      };
    }
  • MCP tool registration for 'set_corner_radius', including Zod input schema (nodeId: string, radius: number >=0, optional corners: boolean[4]) and handler that proxies the command to the Figma plugin via sendCommandToFigma.
    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)
                  }`,
              },
            ],
          };
        }
      }
    );
  • Dispatch handler in the Figma plugin's command router that calls the setCornerRadius implementation.
    case "set_corner_radius":
      return await setCornerRadius(params);
  • Helper function filterFigmaNode extracts and includes cornerRadius when serializing node data for MCP responses.
    if (node.cornerRadius !== undefined) {
      filtered.cornerRadius = node.cornerRadius;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Set' implies a mutation, the description doesn't clarify whether this operation is reversible, what permissions are required, or how it interacts with other node properties. It also doesn't mention error conditions (e.g., invalid node IDs) or whether changes are immediate. For a mutation tool with zero annotation coverage, this represents significant gaps in transparency.

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, direct sentence that efficiently communicates the core purpose without any fluff. It's front-loaded with the essential action and target, making it immediately scannable. Every word earns its place, and there's no redundant or verbose phrasing.

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 that this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like error handling, side effects, or response format. While the schema covers parameters well, the overall context for safe and effective use is lacking, especially compared to sibling tools that may have overlapping or complementary functionalities.

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 three parameters thoroughly. The description adds no additional parameter information beyond what's in the schema (node ID, radius value, optional corner specification). Since the schema does the heavy lifting, the baseline score of 3 is appropriate—the description neither compensates for gaps nor adds meaningful semantic context.

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 target ('corner radius of a node in Figma'), making the purpose immediately understandable. It distinguishes 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' or 'move_node' beyond the specific 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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing a valid node ID from another tool), nor does it specify when corner radius modification is appropriate versus other styling tools. With multiple 'set_' sibling tools available, the lack of comparative context leaves usage decisions ambiguous.

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/paragdesai1/parag-Figma-MCP'

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