Skip to main content
Glama
tathagat22

Plumb (plumb-mcp)

by tathagat22

Plumb · assets

plumb_assets
Idempotent

Export Figma assets as SVG icons and PNG images via a paired plugin. Supports default, list, and surgical modes for targeted or broad exports.

Instructions

Export Figma assets — icons as SVG, images as PNG — through the paired plugin. Three modes: • Default — id or name of a screen → recursive export of every asset in it, written to a local folder. • List — same + list: true → just the manifest (id, name, format, parentId) of available assets; no files written. Cheap; use first to see what's there. • Surgical — ids: [...] → export exactly those node ids (one file each, no recursion). Preferred once you know what you need.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoScreen/node id to scope the export to.
idsNoSurgical — export exactly these node ids (one each, no recursion).
rawNoFor nodes with IMAGE fills, export the original uploaded bytes (JPG/PNG/GIF/WEBP) via getImageByHash, instead of a 2× rasterised PNG render. Other nodes (icons, vectors) export the same as default.
listNoManifest only — return id/name/format/parentId per candidate; no file writes.
nameNoScreen name — resolved against the file.
inlineNoReturn asset bytes inline on each row: SVGs as raw markup, bitmaps under 64KB as a data: URI. Useful for dropping SVG icons straight into JSX without re-reading from disk. Files are still written; this is additive.
Behavior5/5

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

Discloses behaviors beyond annotations: List mode writes no files and is cheap, Surgical exports exact node ids without recursion, inline adds data to responses. Annotations (idempotentHint: true) are consistent; no contradiction.

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?

Concise, well-structured with bullet points and plain English. Every sentence adds value; no redundancy.

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?

No output schema, but description partially covers return values: manifest details for List, file writing behavior, inline data format. Could be more explicit about output structure for Default/Surgical, but sufficient for selection.

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

Parameters4/5

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

Schema covers all 6 parameters (100% coverage), so baseline is 3. Description adds significant value by linking parameters to modes (e.g., 'id/name for Default', 'list: true' for List, 'ids' for Surgical) and explaining behaviors like raw and inline.

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?

Description clearly states 'Export Figma assets — icons as SVG, images as PNG' and defines three distinct modes (Default, List, Surgical), making the tool's purpose specific and differentiating it from siblings.

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?

Explicitly explains when to use each mode: Default for recursive export, List for cheap discovery (recommended first), Surgical for specific node ids. Provides clear alternatives within the tool.

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/tathagat22/plumb-mcp'

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