Skip to main content
Glama
andreycretsu

Cursor Talk to Figma MCP

by andreycretsu

set_corner_radius

Modify corner radius values on Figma design elements to adjust visual styling and create rounded edges for specific 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

  • Full registration of the 'set_corner_radius' tool including schema definition, input validation with Zod, and the handler function 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)
                  }`,
              },
            ],
          };
        }
      }
    );
  • The handler function executes the tool logic: sends 'set_corner_radius' command to Figma plugin with parameters, handles response or error, and returns MCP-formatted content.
    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)
                }`,
            },
          ],
        };
      }
    }
  • Zod schema for input validation: requires nodeId and radius (non-negative number), optional corners array of exactly 4 booleans.
    {
      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]"
        ),
    },
  • In filterFigmaNode helper function, preserves cornerRadius property when filtering node data for 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 the full burden. It states the action 'set' but lacks details on behavioral traits like whether it modifies existing properties, requires specific permissions, or has side effects. For a mutation tool with zero annotation coverage, this is a significant gap 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 with zero waste. It front-loads the core action and resource efficiently, making it easy to parse and understand without unnecessary elaboration.

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?

Given the tool's moderate complexity (3 parameters, no output schema, and no annotations), the description is minimally adequate. It states what the tool does but lacks context on usage, behavioral details, or output expectations, leaving gaps that could hinder an agent's effective 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?

The input schema has 100% description coverage, with clear documentation for nodeId, radius, and corners. The description adds no additional meaning beyond what the schema provides, such as explaining the units for radius or the default behavior if corners is omitted. 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 verb 'set' and the resource 'corner radius of a node in Figma', making the purpose specific and understandable. It distinguishes itself from siblings like set_fill_color or set_stroke_color by focusing on corner radius, though it doesn't explicitly contrast with them beyond the naming.

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, such as needing a valid node ID, or compare it to similar tools like set_layout_mode or set_padding, leaving the agent to infer usage from context 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/andreycretsu/cursor-talk-to-figma-mcp-main'

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