Skip to main content
Glama
the-real-talk

the-real-talk

delete_component_property

Removes a property from a component set or component in Figma, given the node ID and property ID. Use it to clean up obsolete properties from your design system.

Instructions

Delete a component property from a component set or component.

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": "delete_component_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
propertyIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 of behavioral disclosure. It states only 'Delete' and omits critical details such as permissions, reversibility, effects on component instances, confirmation requirements, and error behavior.

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?

The description is a single front-loaded sentence with no redundant wording. Its brevity reflects missing information rather than poor structure, but the sentence itself is clear and efficient.

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 destructive two-parameter mutation with no annotations and no output schema, the definition is too thin. It identifies the operation but omits parameter meaning, safety context, and effects on the component property being removed.

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%, and the description does not explain nodeId or propertyId, their formats, or their constraints. The phrase 'component set or component' gives slight context for nodeId, but neither required parameter is meaningfully documented.

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?

The description names a specific verb and resource: 'Delete a component property', with a clear target of 'a component set or component'. It does not explicitly distinguish this from sibling operations such as edit_component_property or add_component_property, so it falls short of a 5.

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 gives no when-to-use, when-not-to-use, prerequisite, or alternative guidance. An agent must infer that this is the removal counterpart to add/edit_component_property solely from the name and sibling list.

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