Skip to main content
Glama
the-real-talk

the-real-talk

set_image_fill

Fill a Figma node with a local image file or base64 data, replacing existing fills. Use to apply images to shapes when remote URLs are not supported.

Instructions

Fill a node in Figma with an image from a local file path or base64 data (replaces the node's existing fills). Remote URLs are not supported.

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": "set_image_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to fill
imagePathNoAbsolute path to a local image file, read by the MCP server (preferred: keeps image bytes out of the model context)
scaleModeNoHow the image fills the node (default: FILL)
imageBase64NoBase64-encoded image data, with or without a data: URI prefix (only when the image exists nowhere else)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does disclose the most important trait: the operation is destructive to the node's existing fills. It omits other behavioral facts an agent might want (plugin/app connection requirements, error behavior for invalid node types, whether the call returns the applied paint).

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

Conciseness5/5

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

A single tight sentence with the core action front-loaded, followed by the destructive-behavior parenthetical and the URL limitation. Nothing is redundant and no clarifying detail is buried.

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

Completeness4/5

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

For a four-parameter mutation tool with a fully documented schema and no annotations or output schema, the description covers the essentials: what it does, accepted inputs, what it overwrites, and what is unsupported. The main remaining gap is the absence of any statement about the return value or failure modes, which the missing output schema leaves entirely to the description.

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

Parameters3/5

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

Schema description coverage is 100%, so all four parameters including the scaleMode enum are already documented in the schema. The description only echoes the source-parameter semantics (path vs base64, no URLs) without adding syntax, format, or default details beyond what the schema states, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource (fill a node with an image) plus the two accepted source types (local file path, base64), which cleanly separates it from the color/paint siblings like set_fill_color and set_paints. The negative constraint 'Remote URLs are not supported' further narrows the tool's identity.

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

Usage Guidelines4/5

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

Gives clear qualifying context: use when the image comes from a local path or base64 data, and explicitly rules out remote URLs. It does not name an alternative tool for the cases it excludes (e.g., what to use for a solid-color fill or a URL-sourced image), so guidance is strong but not complete.

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

Deploy Server

Other Tools