figlens

Overview Schema Source Related Servers Discussions Admin

bundle

Export a ZIP package for a selected Figma node or exact instance sublayer, including nodes, variables, assets, a reference render, and context.md; optionally add related component states.

Instructions

Write a design bundle zip for one node or exact instance sublayer: nodes, variables, assets, reference render, context.md. When the user requests related component states, pass states=true to include their explicit variants and evidence gaps; no MCP configuration change is needed.

Input Schema

Name	Required	Description
`out`	Yes	output path for the bundle ZIP; unless the user names one, use .figlens/exports/ under the project root, created with a .gitignore containing * so it stays out of Git; create the parent directory first
`file`	Yes	the saved .fig: a local path (absolute recommended), or gs://bucket/object using gcloud; remote sources are unavailable with --root
`name`	No	frame name for the manifest
`node`	Yes	a stored node id (12:345 or 12-345), full instance sublayer id (I12:345;67:89) from inspect/nodes, or a Figma URL with ?node-id=
`states`	No	include design/states.json and a bounded context.md summary; retains inspect's source, unknown and truncation markers; default false
`fileKey`	No	Figma file key for the manifest

Output Schema

Name	Required	Description
`path`	Yes
`nodeId`	Yes
`warnings`	Yes	missing assets, known rendering limits and truncated optional state inventory; missing-assets.json contains only asset failures; design/nodes.json has per-node _figlens.renderDiagnostics; design/states.json has inventory coverage when requested

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.9.3Oct 29, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

changedInput schema / properties / out / description

Previous value: -"output path for the bundle ZIP; create the parent directory first"New value: +"output path for the bundle ZIP; unless the user names one, use .figlens/exports/ under the project root, created with a .gitignore containing * so it stays out of Git; create the parent directory first"

Changed8 schema fields changedv0.7.2Oct 26, 2026

addedInput schema / additionalProperties
```
Added value: +true
```

changedInput schema / properties / file / description

Previous value: -"the .fig file (File > Save local copy): an absolute path, or gs://bucket/object"New value: +"the saved .fig: a local path (absolute recommended), or gs://bucket/object using gcloud; remote sources are unavailable with --root"

addedInput schema / properties / file / minLength
```
Added value: +1
```

changedInput schema / properties / node / description

Previous value: -"a node id (12:345 or 12-345) or a Figma URL with ?node-id="New value: +"a stored node id (12:345 or 12-345), full instance sublayer id (I12:345;67:89) from inspect/nodes, or a Figma URL with ?node-id="

changedInput schema / properties / out / description

Previous value: -"absolute path of the .zip to write"New value: +"output path for the bundle ZIP; create the parent directory first"

addedInput schema / properties / out / minLength
```
Added value: +1
```

addedInput schema / properties / states

Added value: +{
+  "default": false,
+  "description": "include design/states.json and a bounded context.md summary; retains inspect's source, unknown and truncation markers; default false",
+  "type": "boolean"
+}

changedOutput schema / properties / warnings / description

Previous value: -"assets the bundle could not include; missing-assets.json has details"New value: +"missing assets, known rendering limits and truncated optional state inventory; missing-assets.json contains only asset failures; design/nodes.json has per-node _figlens.renderDiagnostics; design/states.json has inventory coverage when requested"

First observedOct 23, 2026

TDQS

A3.5/5.0

Behavior3/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. It discloses the bundle contents and that states preserves inspect's source/unknown/truncation markers, but omits whether the source .fig is mutated, error/failure behavior, and access prerequisites for local vs gs:// sources.

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?

Two dense sentences, front-loaded with the action and scope before the states caveat. Slightly jargony ("instance sublayer", "evidence gaps") but no wasted clauses.

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

Completeness4/5

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

With 100% parameter coverage and an output schema, the description needn't explain return values. It covers the bundle contents and states toggle adequately; only mutation semantics and failure handling for the write operation are left unstated.

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?

100% schema description coverage means the baseline is 3; the description adds little beyond it. It does map the user's "related component states" intent onto states=true, but node/file/out meaning stays in 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?

States a specific verb ("Write") and resource ("design bundle zip") scoped to "one node or exact instance sublayer," then enumerates what the bundle contains. An agent can distinguish this from export/inspect, though it never names the sibling it replaces.

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

Usage Guidelines3/5

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

Gives conditional guidance for the states flag ("When the user requests related component states, pass states=true") and reassures that no config change is needed. However, it never says when to use this tool versus export/verify/nodes, leaving the main routing decision implicit.

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

Deploy Server