Skip to main content
Glama

figma_create_ellipse

Creates an ellipse node in a Figma file using precise x, y, width, and height values, with optional fill, name, and parent placement.

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_ellipse"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fillNo
nameNo
widthYes
heightYes
parentIdNo

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 bears the full behavioral disclosure burden, yet it says nothing about mutation effects, which page or frame the ellipse lands on, whether an existing selection affects placement, or what the call returns. For a write operation with zero annotation coverage this is a serious omission.

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?

The single sentence is free of waste but is under-specified rather than concise, so brevity here is a liability. There is no structure to front-load because no substantive information exists.

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?

The tool takes seven parameters, four of them required, with a nested object and no output schema or annotations, so the description should carry substantial weight. Instead it offers nothing about geometry semantics, coordinate space, fill format, or return value, leaving the definition wholly inadequate for correct invocation.

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 seven parameters, including a nested fill object with r/g/b/a components and an opaque parentId string, and the description supplies no compensating explanation of any parameter. Units for x/y/width/height and the meaning of parentId omission are left entirely undefined.

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?

The description "创建椭圆" (create an ellipse) merely restates the tool name figma_create_ellipse, adding no scope, target container, or distinguishing detail. An agent learns nothing it did not already know from the identifier, and cannot tell from the text how this differs from figma_create_rectangle 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 guidance on when to use this tool versus the sibling creation tools, no prerequisite such as selecting a page or knowing the parent frame, and no note about whether parentId is required for placement. The agent must infer all usage context from the name alone.

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