Skip to main content
Glama
the-real-talk

the-real-talk

delete_variable_collection

Remove a Figma variable collection by ID or name, including all variables within it, to clean up unused design tokens.

Instructions

Delete a variable collection (ID or name) and all its variables.

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": {
      "collection": "<collection>"
    },
    "name": "delete_variable_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
collectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/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 does disclose the key side effect — that all variables inside the collection are deleted too — which is genuinely useful context beyond structured data. However, it says nothing about irreversibility, required permissions, or what happens if the identifier does not resolve to an existing collection.

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?

One sentence, front-loaded with the destructive verb and the cascade consequence. Nothing is redundant or padded.

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?

For a destructive, irreversible mutation with no annotations and no output schema, the description covers the essential cascade behavior and accepted identifier forms but omits failure modes and confirmation/irreversibility warnings. Adequate but leaves meaningful gaps for a delete operation.

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 0% for a single required string parameter, so the description must compensate. The parenthetical "(ID or name)" does exactly that, telling the agent both identifier forms are accepted — the main ambiguity an agent would otherwise face.

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?

States a specific verb and resource ("Delete a variable collection") and scopes the target to "ID or name". The cascade clause distinguishes it from delete_variable, which removes a single variable rather than a collection, though it does not explicitly contrast with rename_variable_collection.

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 guidance on when to choose this over delete_variable or the collection-management siblings, and no stated prerequisites or preconditions for a destructive operation. The agent must infer usage entirely from the name and the phrase 'and all its variables'.

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