Skip to main content
Glama
haju-xp

figma-free-mcp

by haju-xp

set_image_filters

Adjust exposure, contrast, saturation, temperature, tint, highlights, and shadows of image fills in Figma. Fine-tune color and light settings for precise image editing.

Instructions

Apply color and light adjustments to image fills

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node with image fill
exposureNoBrightness adjustment (-1.0 to 1.0)
contrastNoContrast adjustment (-1.0 to 1.0)
saturationNoColor intensity (-1.0 to 1.0, -1 = grayscale)
temperatureNoWarm/cool tint (-1.0 to 1.0)
tintNoGreen/magenta shift (-1.0 to 1.0)
highlightsNoBright area adjustment (-1.0 to 1.0)
shadowsNoDark area adjustment (-1.0 to 1.0)
Behavior2/5

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

With no annotations, the description should disclose behavioral traits like whether adjustments are additive or absolute, or if nodeId must reference a valid image fill. The one-line description omits these details.

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?

The description is a single concise sentence with no redundancy. It could be slightly expanded to include core behavior, but it is efficiently front-loaded.

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?

The tool has 8 parameters and no output schema, yet the description provides no context about combining filters, defaults ordering, or error cases. It is insufficient for reliable invocation.

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?

All 8 parameters have schema descriptions, so the description adds limited value. It summarizes 'color and light adjustments' but doesn't clarify how parameters interact or what default values are, meeting the baseline.

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 clearly states the tool applies color and light adjustments to image fills, conveying the main action and target. However, it does not differentiate from similar sibling tools like set_image_fill or set_effects, which could cause confusion.

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 is provided on when to use this tool versus alternatives, nor any conditions or prerequisites. The description lacks explicit usage context.

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