Skip to main content
Glama
the-real-talk

the-real-talk

bind_variable_field

Bind a variable to a Figma node field such as size, spacing, color-related weights, or visibility to control design values. Unbind by passing a null variableId.

Instructions

Bind (or unbind with variableId null) a variable to any bindable node field: height, width, characters, itemSpacing, paddingLeft, paddingRight, paddingTop, paddingBottom, visible, topLeftRadius, topRightRadius, bottomLeftRadius, bottomRightRadius, minHeight, maxHeight, minWidth, maxWidth, strokeWeight, strokeTopWeight, strokeRightWeight, strokeBottomWeight, strokeLeftWeight, opacity, counterAxisSpacing, fontFamily, fontSize, fontStyle, fontWeight, letterSpacing, lineHeight, paragraphSpacing, paragraphIndent. Use a FLOAT variable for numeric fields, BOOLEAN for visible, STRING for characters, fontFamily and fontStyle.

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>",
      "field": "<field>",
      "variableId": "<variableId>"
    },
    "name": "bind_variable_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYes
nodeIdYes
variableIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It discloses that passing null unbinds and that types must match, but it says nothing about required permissions, what happens on an incompatible variable type, whether an existing binding is replaced, or error behavior for a mutation tool.

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?

Two sentences, front-loaded with the core bind/unbind behavior. The long field enumeration is verbose but necessary for the tool's scope, and there is no filler.

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?

For a three-parameter mutation tool with no annotations and no output schema, the definition covers the core operation, unbind path, and type constraints. It omits permissions, failure behavior, and replacement semantics, leaving meaningful gaps an agent would want before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does for two parameters: variableId's null value is given explicit unbind semantics, and the type-to-field mapping adds meaning the schema's bare string/null type does not convey. nodeId is left unexplained, and the field list largely mirrors the enum.

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 gives a specific verb and resource: bind (or unbind) a variable to a named node field, and enumerates the supported field set. This makes the field-level scope clear, though it never explicitly contrasts itself with the sibling bind_variable, leaving the agent to infer that distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the unbind condition (variableId null) and the variable-type requirements per field category (FLOAT for numeric, BOOLEAN for visible, STRING for characters/fontFamily/fontStyle). It does not name the alternative tool for whole-node binding or mention prerequisites, so context is clear but incomplete.

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