Skip to main content
Glama
the-real-talk

the-real-talk

set_node_properties

Batch-update many Figma node properties in one whitelist-validated call, covering layout, sizing, visibility, and text settings to build and adjust designs consistently.

Instructions

Set many node properties at once, validated against a whitelist. Numbers: opacity, rotation, x, y, width, height (resize; makes the size FIXED), itemSpacing, padding*, strokeWeight, stroke{Top,Right,Bottom,Left}Weight (per-side inner borders), cornerSmoothing, topLeftRadius..bottomRightRadius, cornerRadius, layoutGrow, paragraphSpacing, paragraphIndent, maxLines. Numbers or null: minWidth, maxWidth, minHeight, maxHeight, counterAxisSpacing. Booleans: visible, locked, clipsContent, isMask, itemReverseZIndex, strokesIncludedInLayout. Strings: name, description (components). Enums: blendMode, layoutMode, layoutWrap (WRAP = flex-wrap), primaryAxisSizingMode, counterAxisSizingMode, primaryAxisAlignItems, counterAxisAlignItems, counterAxisAlignContent, layoutAlign, layoutPositioning, layoutSizingHorizontal, layoutSizingVertical, strokeAlign, strokeJoin, strokeCap, textAutoResize, textAlignHorizontal, textAlignVertical, textCase, textDecoration, textTruncation, leadingTrim. Objects: constraints {horizontal, vertical}; dashPattern [numbers].

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>",
      "properties": "<properties>"
    },
    "name": "set_node_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
propertiesYes{property: value}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real behavioral content: properties are validated against a whitelist, and height/width resizing forces size to FIXED, a non-obvious side effect. It omits what happens on an invalid key (error vs. silent ignore), whether omitted properties are reset, permission requirements, and return 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence states the action and validation rule up front, then the long tail is organized into labeled type groups (Numbers, Booleans, Strings, Enums, Objects). Given that the properties bag is untyped, essentially every key listed earns its place.

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 mutation tool with no annotations, no output schema, and a free-form properties parameter, the description names valid keys but never states allowed values for the enum fields, reset/omission behavior, or failure modes. It is substantially better than nothing but leaves the agent guessing on execution details.

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 coverage is 50%, and crucially the `properties` object is free-form (additionalProperties only), so this description is the sole documentation of legal keys. It usefully partitions keys by value type, flags nullable fields (minWidth, maxWidth, counterAxisSpacing), and gives the shape of object-valued keys (constraints, dashPattern). It says nothing about the nodeId parameter's semantics.

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?

"Set many node properties at once, validated against a whitelist" gives a specific verb and resource plus the batch scope, which implicitly distinguishes it from the many single-property siblings. It does not, however, explicitly name any of those siblings (set_corner_radius, set_item_spacing, set_layout_mode) as the narrower alternatives.

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?

There is no explicit when-to-use or when-not-to-use guidance and no prerequisites or preconditions stated. The reader can infer that batch-edit is preferable to many single-property calls, but that inference is never made explicit, and no alternatives are named.

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