Skip to main content
Glama
Sign In
Talk to Figma MCP

Talk to Figma MCP

by kctw-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

set_instance_properties

Changes component properties on a Figma instance, enabling variant switching such as Platform from Desktop to Mobile.

Instructions

Set component properties on an instance (e.g. switch Platform from Desktop to Mobile)

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
nodeIdYesThe instance node ID
propertiesYesProperties to set, e.g. {"Platform": "Mobile"}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It describes the action as setting properties, but does not mention side effects, permissions, or error conditions. It is not misleading but lacks depth.

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 description is a single sentence with an example, front-loading the key information. No wasted words; every part earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With two parameters and no output schema, the description adequately covers purpose and usage. It lacks details about return values, but for a mutation tool this is acceptable. Given the complexity, it is sufficiently complete.

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% with descriptions for both parameters. The description adds value by providing an example property object, which clarifies the expected format beyond the schema's generic description.

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 explicitly states 'Set component properties on an instance' with a concrete example (switch Platform from Desktop to Mobile). This clearly differentiates from sibling tools like set_instance_overrides, which likely set different types of properties.

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?

The description provides an example usage, but does not explicitly state when to use this tool versus alternatives like set_instance_overrides. However, the context of 'component properties' vs 'overrides' is implied.

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