Skip to main content
Glama
the-real-talk

the-real-talk

rename_variable

Updates a Figma variable's name using its ID to keep design-system tokens clear and consistent.

Instructions

Rename 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": "<name>"
    },
    "name": "rename_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
variableIdYes

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?

With no annotations at all, the description carries the full behavioral burden and it does not deliver: it never states that this is a mutation, whether the old name is preserved anywhere, whether existing bindings follow the rename, or what happens if the ID or new name is invalid. Only the bare 'Rename' verb implies mutation.

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?

A single short sentence with no filler, and the identifying detail ('by ID') is placed where it is read first. It is terse rather than padded, though it lands close to under-specification.

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 an unannotated mutation tool with 0% schema description coverage and no output schema, this definition provides almost nothing beyond the name. An agent can guess the call shape but cannot predict side effects, error conditions, or how the rename interacts with variable bindings.

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 neither 'variableId' nor 'name' is documented structurally. The description only implies that variableId is the target and that a new name is supplied; it says nothing about format constraints, uniqueness, or naming rules for the new name.

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 supplies a specific verb ('Rename') and resource ('a variable'), plus an addressing hint ('by ID'), so the agent knows exactly what the operation does. It does not, however, distinguish this tool from siblings such as rename_variable_collection or rename_variable_mode, which share the same verb.

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 precondition (e.g., variable must be local/remote, must exist), and no pointer to the collection- or mode-scoped rename variants. The agent must infer selection from the name alone.

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