Skip to main content
Glama
the-real-talk

the-real-talk

set_instance_properties

Set text and variant component properties on a Figma instance by property name and value, enabling dynamic updates to instances in a design system.

Instructions

Set component properties of an instance: a text property by its short name (e.g. Libellé) or variant properties (e.g. Style, État) with their value.

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_instance_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesID of the instance
propertiesYes{property name: value}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It reveals that the operation is a mutation but says nothing about prerequisites (must the node be an instance of a component?), what happens to values not listed, whether changes are reversible, or how failures surface when a property name is unknown.

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?

A single front-loaded sentence with the resource first and the two property categories after the colon. No filler, though the parenthetical example pairs make it slightly denser than necessary.

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 two-parameter tool with a fully documented schema this is close to sufficient, but with zero annotations and no output schema the description should still say what state the instance must be in and roughly what success means.

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 100%, so the baseline is 3; the description earns more by explaining the semantics of the nested properties object — keys are short property names, values may be text strings or variant values — with concrete examples beyond the schema's bare '{property name: value}'.

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?

States a specific verb and resource: it sets component properties on an instance, and clarifies the two kinds handled (text properties by short name, variant properties by value). This implicitly distinguishes it from set_node_properties, though it never names a sibling explicitly.

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?

Usage is implied by the phrase 'component properties of an instance', but there is no explicit when-to-use guidance and no mention of when to prefer set_instance_overrides, set_node_properties, or set_component_property_reference instead.

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