Skip to main content
Glama
the-real-talk

the-real-talk

detach_instance

Detaches a Figma instance into a plain frame, converting an instance node into editable layers so you can modify its structure directly.

Instructions

Detach an instance into a plain frame.

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": "detach_instance"
  }
}

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 supplied, so the description carries the full disclosure burden and does not meet it. 'Into a plain frame' hints that the component link is severed, but it never says the operation is irreversible, what happens to existing overrides or child layers, or whether the original component is affected.

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?

One front-loaded sentence with no filler or redundant restatement of the name. It is efficiently written, though the brevity contributes to the coverage gaps noted elsewhere.

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 a destructive, irreversible mutation with zero annotations, no output schema, and an undocumented parameter, the description is too thin. It should at minimum state irreversibility and what the caller retains (children, overrides) after detachment.

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% for the single required nodeId parameter, and the description never mentions it. The agent gets no confirmation that nodeId refers to the instance being detached, nor any constraints on its form (key vs. id).

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 (detach) and the resulting resource state (a plain frame), which is concrete enough to distinguish it from siblings like swap_instance or reset_instance_overrides. It stops short of naming those alternatives, so an agent must infer the boundary from the verb alone.

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 and no mention of alternatives or prerequisites. An agent must already know that detaching breaks the component link and is the appropriate action only when the instance should become standalone.

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