Skip to main content
Glama
Sign In
Talk to Figma MCP

Talk to Figma MCP

by kctw-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

bind_variable_to_fill

Bind a Figma variable to a node's fill color to update the fill automatically when the variable changes.

Instructions

Bind a Figma variable to a node's fill color

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>",
      "variableName": "<variableName>"
    },
    "name": "bind_variable_to_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to bind the variable to
variableNameYesThe name of the Figma variable to bind

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only states the core action but omits critical behavioral details: whether existing fills are replaced, what happens if the variable doesn't exist, side effects, or required permissions.

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?

Description is a single, efficient sentence that conveys the core purpose without extraneous words. It is front-loaded and wastes no space.

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?

Given the tool's simplicity (2 params, no output schema), the description provides the essential purpose. However, missing behavioral context (e.g., fill replacement behavior, variable existence handling) limits completeness for a fully informed agent.

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 coverage is 100% with descriptions for both parameters. The description adds no additional meaning beyond what the schema already provides, so baseline score of 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?

Description clearly states the action: bind a Figma variable to a node's fill color. The verb 'bind' and resource 'variable to fill' are specific, and it distinguishes from sibling tool bind_variable_to_stroke by specifying 'fill' vs 'stroke'.

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?

Description implies usage (when you want to set fill via variable) but provides no explicit guidance on when to use this vs alternatives like set_fill_color, nor any prerequisites or when-not-to-use.

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