Skip to main content
Glama
haju-xp

figma-free-mcp

by haju-xp

set_image_fill

Apply an image to a Figma node using a URL or base64 data string, with optional scaling modes like fill, fit, crop, or tile.

Instructions

Apply image to node from URL or base64 data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to apply image to
imageSourceYesImage URL or base64 data string
sourceTypeYesSource type: 'url' for image URL, 'base64' for base64 encoded data
scaleModeNoImage scaling mode (default: FILL)
Behavior2/5

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

No annotations provided, and the description only states the action without disclosing side effects (e.g., overrides existing fills, required permissions, error handling). The burden is on the description, which is insufficient.

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 description is very concise (one sentence) but lacks any structural elements like use cases or examples. It is minimally acceptable but could benefit from more detail.

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?

No output schema. The tool modifies a node, but the description does not mention return values, success conditions, or consequences of failure. Incomplete for a mutation tool.

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 the schema already explains each parameter. The description adds no extra meaning beyond 'from URL or base64 data'. Baseline score of 3 applies.

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 states a specific verb ('Apply image') and resource ('node') with source types (URL or base64). It is clear but does not distinguish from similar sibling tools like 'set_image' or 'replace_image_fill'.

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?

No guidance on when to use this tool versus alternatives. The description implies a general setting of image fill but does not specify exclusions (e.g., when to use replace_image_fill instead).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/haju-xp/figma-free-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server