Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

set_image_fill

Apply an image fill to a Figma node from a URL, with configurable scale modes for fitting, cropping, or tiling. Use this to populate node backgrounds with external images.

Instructions

Set an image fill on a node from 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": {
      "nodeId": "<nodeId>",
      "url": "<url>"
    },
    "name": "set_image_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesImage URL
nodeIdYesTarget node ID
scaleModeNoScale mode (default: FILL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says what the tool does, not whether it replaces existing fills, how it handles invalid URLs, whether image loading is synchronous, or any side effects beyond the basic mutation.

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, front-loaded sentence with no filler or redundant wording. Every word earns its place, and the core operation is immediately clear.

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

Completeness3/5

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

The tool is simple and the schema fully documents all parameters, but with no annotations and no output schema, the description leaves out useful operational context like whether the image fill replaces existing fills or whether the URL must be publicly accessible. Adequate for basic invocation, but not complete for confident autonomous use.

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%, with each parameter already documented meaningfully: nodeId is 'Target node ID', url is 'Image URL', and scaleMode has an enum plus default. The description adds no additional parameter semantics beyond reinforcing the URL source.

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?

The description states a specific verb ('Set'), a specific resource ('an image fill'), and the source mechanism ('from URL'). It clearly distinguishes this from sibling tools like set_fill or set_gradient_fill by specifying the image-fill type.

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 description implies the tool should be used when an image fill is desired, but it does not explicitly state when to choose this over alternatives such as set_gradient_fill or set_fill. No exclusion criteria or alternative routing is provided.

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