Skip to main content
Glama

figma_create_frame

Creates a Figma frame at specified coordinates and size on the current page or inside a parent node, enabling precise layout reconstruction and nested Auto Layout structures.

Instructions

在当前页或指定父节点创建 Frame。复刻时优先嵌套 Auto Layout;按钮用 Frame 包文案并居中。

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
nameNo
widthYes
heightYes
parentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does add real behavioral context beyond the schema by disclosing that the frame lands on the current page when no parent is given, but it is silent on what is returned (no output schema exists, so the agent cannot learn the new node's id), the coordinate origin, and whether the operation fails silently or errors.

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 the core action and placement scope front-loaded, then implementation advice. Nothing is redundant, though the Auto Layout/button sentence is prescriptive style guidance rather than tool-specific information.

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?

A 6-parameter creation tool with no annotations and no output schema needs considerably more: parameter meanings, coordinate semantics, and return value are all absent. The description covers purpose and a design convention but leaves an agent unable to call it precisely without inspecting the schema and guessing.

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 description must compensate and largely does not. It only implicitly explains parentId's optionality via '当前页或指定父节点'; x, y, width, height and name are never mentioned, leaving units and coordinate reference frame undefined.

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 opens with a specific verb+resource ('创建 Frame') and states placement scope ('在当前页或指定父节点'). This clearly separates it from figma_create_rectangle, figma_create_ellipse and other sibling creators without needing to name them. It stops short of explicit sibling differentiation, so 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence gives design-workflow guidance ('复刻时优先嵌套 Auto Layout', buttons should wrap text in a Frame and center), which implies the intended context: building or replicating layouts. However, it never states when NOT to use this tool versus a rectangle or group, and the guidance is stylistic rather than selection criteria.

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