Skip to main content
Glama
the-real-talk

the-real-talk

reset_instance_overrides

Clears all overrides on a Figma instance by node ID, restoring it to its master component's default appearance. Use it to undo custom text, fills, or property changes made to a single instance.

Instructions

Reset all overrides of an instance.

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

Input Schema

NameRequiredDescriptionDefault
nodeIdYes

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 provided, so the description carries the full burden. 'Reset all overrides' does imply a destructive mutation that discards existing override values, but the description never confirms irreversibility, which override categories are affected, or whether the underlying component definition is touched.

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 front-loaded sentence with no filler. It is efficient rather than padded; the shortfall is missing information, not wasted wording.

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?

Although the tool is simple (one parameter, no nested objects), it is an irreversible mutation with no annotations, no output schema, and zero parameter documentation. An agent lacks enough information to know what will be destroyed or what state the instance ends up in.

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?

The single parameter nodeId has 0% schema description coverage, so the schema says only that it is a non-empty string. The description's phrase 'of an instance' weakly implies nodeId identifies the instance, but it never states that the parameter takes an instance node ID or how to obtain one.

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 gives a specific verb ('Reset') plus scope ('all overrides of an instance'), which cleanly separates it from get_instance_overrides and set_instance_overrides among the siblings. It is terse but the action and target are unambiguous.

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 explicit when-to-use or when-not-to-use guidance. The agent must infer from the name alone that this is the inverse of set_instance_overrides, and nothing states prerequisites such as the node having to be a component instance.

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