Skip to main content
Glama
the-real-talk

the-real-talk

add_component_property

Adds TEXT, BOOLEAN, or INSTANCE_SWAP properties to a Figma component or component set and returns the property ID for binding references.

Instructions

Add a TEXT, BOOLEAN or INSTANCE_SWAP (defaultValue = ID of a local component) component property to a component set (or a component). Returns the propertyId to reference with set_component_property_reference.

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>",
      "name": "<name>",
      "type": "<type>",
      "defaultValue": "<defaultValue>"
    },
    "name": "add_component_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesProperty name
typeYes
nodeIdYesID of the component set
defaultValueYesDefault value (string for TEXT, boolean for BOOLEAN)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the mutation ('Add'), the return value (propertyId), and that INSTANCE_SWAP defaultValue must be the ID of a local component, but it omits permissions, side effects on existing instances, uniqueness rules, and reversibility.

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?

Two tightly written sentences with the action and return value front-loaded. The parenthetical about defaultValue is efficient and no wording is wasted.

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?

The description gives enough to make the call: supported types, target, default value rule, and return value. However, for a mutation tool with no annotations and no output schema, it should do more to explain side effects, permissions, and whether existing references are affected.

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 75%, and the description adds meaning beyond the schema by clarifying that INSTANCE_SWAP defaultValue is the ID of a local component and that nodeId targets a component set or component. The schema already documents name and most defaultValue rules, so this is a solid supplement rather than a full substitute.

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 opens with a specific verb ('Add') and resource ('component property'), enumerates the supported property types, and names the follow-up tool set_component_property_reference. This lets an agent distinguish creation from editing or deletion without opening the schema.

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 gives clear workflow context: use this to create a property, then use the returned propertyId with set_component_property_reference. It does not explicitly state when to prefer this over edit_component_property or when not to use it, so it falls short of full when/when-not guidance.

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