Skip to main content
Glama
the-real-talk

the-real-talk

delete_variable

Delete a design system variable from Figma by its ID. Use it to remove an unneeded variable and keep your variable collections clean.

Instructions

Delete a variable by ID.

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": {
      "variableId": "<variableId>"
    },
    "name": "delete_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
variableIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. The word 'Delete' signals a destructive mutation, but the description never states whether deletion is permanent or reversible, what happens to bindings or aliases referencing the variable, whether permissions are required, or how failures are reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no wasted words and is front-loaded with the action. The brevity, however, reads as under-specification rather than disciplined concision, since nothing beyond the minimum is conveyed.

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 mutation tool with no annotations, no output schema, and an undocumented parameter, the definition is too thin. An agent lacks the information needed to call it safely, particularly consequences for existing bindings and irreversibility.

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?

With one parameter and 0% schema description coverage, the description must compensate and barely does. 'By ID' hints that variableId identifies the target, but it adds no format, source, or validity information beyond the schema's property name and minLength constraint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Delete a variable by ID'), so the core action is unambiguous. However, it does not distinguish this tool from the sibling delete_variable_collection or explain that it targets a single variable rather than a collection, leaving the boundary between the two to be inferred from names alone.

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?

There is no when-to-use guidance, no prerequisite conditions, and no mention of alternatives such as delete_variable_collection. The agent must decide entirely on its own when this tool is appropriate.

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