Skip to main content
Glama

figma_create_image

Create rectangle or SVG image nodes in Figma from local image files with precise position and size; remote URLs are not supported.

Instructions

从本机图片文件创建矩形或 SVG 节点。不支持远程 URL。色块不能当成已经插图。

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
nameNo
widthYes
heightYes
parentIdNo
imagePathYes
scaleModeNo
cornerRadiusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations at all, the description must carry the behavioral burden. It usefully discloses the local-file-only constraint and what node types get produced, but says nothing about coordinate/parent semantics, failure modes, whether the image is uploaded, or how scaleMode affects the result.

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

Conciseness3/5

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

The core action is front-loaded in a short first sentence and the URL exclusion follows immediately. However, the final sentence ('色块不能当成已经插图') is vague and arguably does not earn its place, since an agent cannot act on it.

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 9-parameter mutation tool with no annotations, no output schema, and zero schema description coverage, the definition is under-specified. An agent would have to guess at geometry, parenting, and scaling behavior before it could call this correctly.

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 9 parameters, so the description needs to compensate and largely does not. It only implies that imagePath is a local filesystem path; x, y, width, height, parentId, name, cornerRadius, and especially the FILL/FIT/CROP/TILE scaleMode enum are left entirely to the bare schema.

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?

States a specific verb and resource: create a rectangle or SVG node from a local image file. That distinguishes it from figma_create_rectangle and figma_create_ellipse by the source being an image asset, though the description never names those siblings explicitly.

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?

Provides one real exclusion ('不支持远程 URL' – remote URLs are not supported), which tells the agent when not to use it. It gives no positive routing guidance versus the other create_* siblings, and the closing sentence about color blocks is too opaque to function as usage guidance.

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