Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk

set_corner_radius

Adjust corner rounding on Figma design elements by specifying radius values and selecting which corners to modify for precise visual styling.

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

  • Direct registration of the 'set_corner_radius' MCP tool using server.tool(), which includes the tool description, Zod input schema, and the async handler function that proxies the command to Figma via websocket.
    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 that executes the 'set_corner_radius' tool logic: sends the command to Figma websocket with parameters, handles the response, and returns formatted text content or error.
    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 input schema defining parameters for the 'set_corner_radius' tool: nodeId (string), radius (non-negative number), corners (optional fixed-length array of 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]"
        ),
    },
  • Higher-level registration function registerTools that calls registerModificationTools(server), indirectly registering set_corner_radius among other tools.
    export function registerTools(server: McpServer): void {
      // Register all tool categories
      registerDocumentTools(server);
      registerCreationTools(server);
      registerModificationTools(server);
      registerTextTools(server);
      registerComponentTools(server);
    }
  • Ultimate call to registerTools(server) in the main MCP server setup, which chains to the registration of set_corner_radius.
    registerTools(server);
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 states this is a mutation operation ('Set'), but doesn't disclose important behavioral traits like whether it requires specific permissions, if changes are reversible, what happens when invalid values are provided, or if there are rate limits. The description is minimal and lacks operational context.

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 communicates the core purpose without any wasted words. It's appropriately sized for a straightforward tool and gets directly to the point with clear subject-verb-object structure.

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 insufficiently complete. It doesn't explain what happens after execution (success/failure indicators), doesn't mention error conditions, and provides no context about the Figma environment or how this operation fits within design workflows. The description meets only the bare minimum for stating what the tool does.

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?

With 100% schema description coverage, the input schema already fully documents all three parameters. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain units for 'radius', provide examples for the 'corners' array, or clarify edge cases. The baseline score of 3 reflects adequate but unenhanced parameter documentation.

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 the target ('corner radius of a node in Figma'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other Figma styling tools like 'set_fill_color' or 'set_stroke_color' beyond the specific property being modified.

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), when not to use it (e.g., on non-rectangular nodes), or how it relates to sibling tools like 'set_effects' that might also affect visual appearance.

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/arinspunk/claude-talk-to-figma-mcp'

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