Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

reset_overrides

Reset a Figma component instance to its default state by clearing all overrides. Restore original properties and styles quickly.

Instructions

Reset all overrides on a component 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_overrides"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesInstance node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, so the description must fully disclose behavioral impact, but it only says 'Reset all overrides'. It does not state that the action is destructive, irreversible, or what specific overrides are cleared, which is a significant gap for a 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?

The description is one short sentence of eight words, front-loaded with the action and target, containing no filler or redundancy. It is appropriately concise for a simple tool.

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 one-parameter tool with no output schema, the description is close to minimal sufficiency, but it lacks explicit behavioral caveats and sibling differentiation. An agent would benefit from knowing whether the instance stays linked and what side effects resetting has, especially given similar sibling tools.

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?

The input schema already documents nodeId as 'Instance node' with 100% coverage. The description adds minimal context by referring to a component instance, but it does not provide any new details about the parameter format, constraints, or accepted values beyond the schema.

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 uses a specific verb, 'Reset', and a specific resource, 'all overrides on a component instance', making the core purpose clear. It does not explicitly contrast with sibling tools like detach_instance, but the scope is understandable.

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?

No guidance is provided about when to use this tool versus alternatives such as detach_instance or set_* style tools. The description does not state whether the instance remains linked after resetting, what prerequisites exist, or when resetting is preferable to other operations.

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