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;
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / corners
      Added value: +{
      +  "description": "Optional array of 4 booleans to specify which corners to round [topLeft, topRight, bottomRight, bottomLeft]",
      +  "items": {
      +    "type": "boolean"
      +  },
      +  "maxItems": 4,
      +  "minItems": 4,
      +  "type": "array"
      +}
    • addedInput schema / properties / nodeId
      Added value: +{
      +  "description": "The ID of the node to modify",
      +  "type": "string"
      +}
    • addedInput schema / properties / radius
      Added value: +{
      +  "description": "Corner radius value",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / required
      Added value: +[
      +  "nodeId",
      +  "radius"
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden for behavioral disclosure. It states the mutation ('Set') but does not disclose side effects, behavior when 'corners' is omitted, node type restrictions, or whether the operation replaces or modifies existing corner radius values. This is a significant gap for a write operation.

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, clear sentence with no unnecessary words. It is front-loaded and appropriately concise for the tool's simplicity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and the schema covers all parameters, but the description lacks any mention of return values, default behavior for the optional 'corners' parameter, or edge cases. Given the lack of annotations and output schema, it is adequate but leaves clear gaps.

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%, meaning all three parameters are already well-documented. The description adds no additional meaning beyond what the schema provides, so 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Set') and resource ('a node in Figma') with the exact property ('corner radius'), clearly distinguishing this from sibling tools like set_fill_color or set_padding. It unambiguously states what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance is provided on when to use this tool versus alternatives. Usage is implied by the name and description, but there are no exclusions, prerequisites, or alternative recommendations, leaving the agent to infer the intended context.

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