Skip to main content
Glama
the-real-talk

the-real-talk

set_variable_description

Updates or replaces the description of an existing Figma variable to clarify its purpose or role, such as a color's function in a design system.

Instructions

Set the description of an existing variable (for example the role of a color). Replaces the existing description.

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>",
      "description": "<description>"
    },
    "name": "set_variable_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
variableIdYesID of the variable
descriptionYesNew description text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description does the important work of disclosing overwrite semantics ("Replaces the existing description"), which an agent needs to know before mutating. However, it omits permission requirements, what happens with an empty string, and behavior for an unknown variableId, leaving real gaps for an unannotated mutation tool.

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 short sentences, front-loaded with the action and immediately followed by the replace semantics and a clarifying example. Nothing extraneous.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter scalar setter with full schema coverage and no output schema, the description covers purpose and overwrite behavior adequately. Only edge-case behavior (invalid ID, clearing the description) is absent, which is minor at this complexity.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so variableId and description are already documented; the baseline is 3. The example ("the role of a color") adds modest meaning about what description text is for, but no format or constraint details beyond the schema.

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?

States a precise verb and resource ("Set the description of an existing variable") and clarifies what a 'description' means with a concrete example (the role of a color), which separates it from sibling mutators like set_variable_alias or set_variable_value. An agent can pick it 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"of an existing variable" implies the precondition that the variable must already exist and points to create_variable first, but there is no explicit guidance about when to use this versus alias/codeSyntax or other metadata setters. Usage is inferred rather than stated.

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