Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk

set_image_filters

Adjust image fills in Figma with controls for exposure, contrast, saturation, temperature, tint, highlights, and shadows.

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?

No annotations provided, and the description lacks details on behavioral traits like mutability, reversibility, or side effects. The agent cannot infer whether this modifies the node in place or returns anything.

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?

Single sentence is concise and front-loaded, but could be expanded with minimal additions. No wasted words.

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?

With 8 parameters, no output schema, and no annotations, the description is insufficient. It does not explain how adjustments combine, default values, or what the result looks like.

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 documents all parameters. The description adds no additional meaning beyond 'adjustments', so baseline 3 is appropriate.

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 'Apply color and light adjustments to image fills' specifies a clear verb (apply) and resource (image fills), distinct from sibling tools like 'replace_image_fill' or 'set_image'.

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 (e.g., 'apply_image_transform', 'replace_image_fill'). The description does not mention prerequisites or excluded scenarios.

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/arinspunk/claude-talk-to-figma-mcp'

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