Skip to main content
Glama
the-real-talk

the-real-talk

edit_component_property

Rename a Figma component property or change its default value by node and property ID; returns the updated property ID for follow-up edits.

Instructions

Rename a component property and/or change its default value. Returns the (possibly new) propertyId.

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>",
      "propertyId": "<propertyId>"
    },
    "name": "edit_component_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
nodeIdYes
propertyIdYes
defaultValueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the mutation scope and the returned propertyId, but omits permissions, side effects of renaming, whether changes are reversible, and error behavior for missing nodes or properties.

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 definition is two short sentences with zero padding. The mutation is front-loaded and the return value is stated immediately after.

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

Completeness2/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 0% schema description coverage, the description is too thin. It gives the purpose and return value but leaves parameter roles and mutation side effects largely unexplained.

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

Parameters2/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 explain the four parameters. It maps name to renaming and defaultValue to changing the default, but never explains nodeId or the required role of propertyId as an input.

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 states a specific verb and resource: rename a component property and/or change its default value. This clearly distinguishes it from siblings such as add_component_property, delete_component_property, and set_component_property_reference.

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?

The description implies editing an existing property but gives no explicit when-to-use guidance, prerequisites, or comparison to alternatives. It does not say to use add_component_property for creation or delete_component_property for removal.

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