Lists SLOT nodes within a Figma instance so you can identify valid insertion points for adding content into component slots.
List SLOT nodes inside an instance (for inserting content into slots).
| Name | Required | Description | Default |
|---|---|---|---|
| instanceId | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. 'List' implies a read-only operation, but nothing is said about return format, ordering, pagination, empty-slot behavior, or whether it errors on non-instance nodes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short, front-loaded sentence with no waste and the resource named first. It is efficient, though arguably too thin for the disclosure burden it carries.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description is the only documentation, and it covers the basic operation adequately for a single-parameter list tool. It falls short on return shape and the handoff to append_to_slot.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate and largely does not. 'Inside an instance' loosely ties instanceId to its meaning, but no ID format, source, or example is given.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and resource (SLOT nodes) plus scope (inside an instance), so an agent immediately knows what it retrieves. It does not distinguish itself from nearby siblings such as get_instance_properties or get_instance_source, which also target instance internals.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The parenthetical '(for inserting content into slots)' implies the workflow context — call this before append_to_slot — but never states when to use it, when not to, or names the follow-up tool explicitly. Usage must be inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.