Skip to main content
Glama

figma_create_rectangle

Creates rectangles in the open Figma file using precise x, y, width, and height values, with optional fill, corner radius, and parent placement for pixel-level layout reconstruction.

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": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "figma_create_rectangle"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fillNo
nameNo
widthYes
heightYes
parentIdNo
cornerRadiusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden and discloses nothing. It does not say whether the rectangle is added to the current page or to parentId, whether it becomes selected, what happens with an invalid parentId, or what the call returns — all critical for a mutation tool.

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

Conciseness2/5

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

Four characters plus a period is not conciseness but under-specification; there is no structure, no front-loaded qualifier, and nothing that earns or explains the brevity.

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

Completeness1/5

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

For a mutation tool with 8 parameters, a nested object, 4 required coordinates/dimensions, no annotations, and no output schema, the definition is completely inadequate. An agent has no basis to supply fill, parentId, or cornerRadius correctly.

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

Parameters1/5

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

Schema description coverage is 0% across 8 parameters, including a nested fill object with r/g/b/a and optional fields like parentId, name, and cornerRadius. The description mentions none of them, so it adds zero meaning where the schema is silent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

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

"创建矩形。" does name a concrete verb and resource, but it adds nothing beyond the tool name figma_create_rectangle — it is a restatement of the identifier in another language. An agent learns no scope, no target surface, and no distinction from figma_create_ellipse or figma_create_frame.

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?

There is no when-to-use guidance at all: no statement of which sibling to prefer, no prerequisite about an active page or selection, and no exclusions. The sibling list shows several create_* alternatives, but the definition itself never routes between them.

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