Skip to main content
Glama

figma_set_corner_radius

Set individual or uniform corner radii on Figma nodes to control rounded corners with precise per-corner values.

Instructions

设置圆角。四角独立优先。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nodeId": "<nodeId>"
    },
    "name": "figma_set_corner_radius"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
radiusNo
topLeftNo
topRightNo
bottomLeftNo
bottomRightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
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 of behavioral disclosure, and it does not say that this is a mutating operation, whether existing radii are overwritten, whether it works on frames, rectangles, or any node, or what permissions are needed. The only behavioral fact disclosed is the precedence between uniform and per-corner values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the core purpose is front-loaded. The terseness borders on under-specification, but nothing in the text is wasted.

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 6-parameter mutation tool with no annotations, no output schema, and zero schema description coverage, the description is far too thin. An agent cannot determine node-type applicability, units, or overwrite behavior from this definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 6 parameters, so the schema alone cannot explain nodeId, radius, topLeft, topRight, bottomLeft, or bottomRight. The description adds only the precedence rule 'per-corner values win over radius'; it says nothing about units, ranges, or whether partial corner specification is allowed.

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 names a specific verb and resource ('设置圆角' / set corner radius), which makes the operation unambiguous and matches the tool name. It does not differentiate itself from siblings such as figma_set_stroke or figma_set_effects, but the purpose itself is clear.

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 given on when to use this tool versus alternatives, or what prerequisites apply (for example, whether a node must be selected or of a particular type). The phrase '四角独立优先' is an intra-parameter precedence rule, not usage guidance.

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