Skip to main content
Glama

create_instance

Create a linked copy of a component master and append it to a parent frame or the page root. Use to reuse design system components in layouts.

Instructions

Create an instance of an existing component. Mutates the canvas — appends a new InstanceNode as the last child of parent (or the active page root if omitted). The instance is LINKED to the component master, so future component edits propagate. Returns the new instance's nodeId.

Use when:

  • Spawning runtime copies of a Component master (buttons, list items, cards)

  • Reusing a design-system component in a fresh layout

  • Programmatic instantiation outside a jsx() tree-build

Returns: { data: { id: "5:42", name: "Button", componentId: "1:2" } }

Parameters beyond schema:

  • node must be a Component node (not Frame, Text, or another Instance). Discover IDs with find_nodes({ type: "COMPONENT" }).

  • parent optional. If parent is auto-layout, the instance enters the flow and inherits sizing rules. If omitted, the instance is placed at the active page root with detached position — may overlap existing content; set explicit position with edit afterwards.

Skip when:

  • Duplicating a non-component node — instance creation will fail; use clone_node instead.

  • Building a subtree from scratch — use jsx with for atomic single-call construction.

Examples: create_instance({node: "1:2"}) // at page root create_instance({node: "1:2", parent: "1:4"}) // inside frame 1:4

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYesComponent node ID (e.g. "1:2") to instantiate
parentNoParent node ID for placement
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: it mutates the canvas, appends as last child of parent or page root, creates a linked instance so edits propagate, and explains optional parent effects (auto-layout vs root placement, potential overlap). Return format is also documented.

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 well-organized: succinct purpose, detailed behavior, usage conditions, return type, parameter details, skip cases, and examples. Every sentence contributes valuable information without redundancy.

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

Completeness5/5

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

Given the tool's complexity (instance creation, linking, optional parent behavior), the description covers all necessary aspects: purpose, behavior, parameters, return value, and edge cases. The lack of an output schema is compensated by an explicit return format example.

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

Parameters5/5

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

Both parameters have 100% schema coverage, but the description adds significant extra meaning: node must be a Component node (not Frame/Text/Instance), with a method to discover such nodes; parent is optional with behavioral consequences (auto-layout vs detached position, need for editing). This goes well 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?

The description clearly states the verb ('Create') and resource ('instance of an existing component'), and explains the action (creates an InstanceNode linked to the component master). It distinguishes from sibling tools like clone_node and jsx by specifying when to use each.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit 'Use when' and 'Skip when' sections provide clear context: when to use (spawning runtime copies, reusing design system components, programmatic instantiation) and when not to use (non-component nodes, building subtrees with jsx). Alternative tools are named (clone_node, jsx).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/musepy/genable'

If you have feedback or need assistance with the MCP directory API, please join our Discord server