Skip to main content
Glama
tathagat22

Plumb (plumb-mcp)

by tathagat22

Plumb · node

plumb_node
Read-onlyIdempotent

Extract a Figma screen or node as a normalized design spec with deduplicated tokens and CSS-shaped node tree, auto-layout resolved to flexbox, for code generation.

Instructions

Extract a Figma screen or node as a compact, normalized Plumb Design Spec (PDS): deduplicated design tokens plus a CSS-shaped node tree, with auto-layout pre-resolved to flexbox. With the Plumb plugin paired, pass a screen id or name (no file key) — duplicate names come back as a match list to disambiguate. On the REST path, pass fileKey + id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNode/screen id to extract.
urlNoPaste a full Figma URL — fileKey and node-id are auto-extracted (the `-` separator is normalised to `:`).
nameNoScreen name — plugin path; resolved against the paired file.
depthNoLevels to disclose. Default 3.
notesNoInclude human-readable notes per node.
fileKeyNoFigma file key — REST path. Omit when the Plumb plugin is paired.
expandAllNoWalk the entire subtree in one call, ignoring `depth`. Subject to `maxTokens` (defaults to 60000 if omitted); if the spec exceeds the budget, depth is auto-trimmed and `meta.truncated` is set. Use this to skip the drill-loop on dense screens.
maxTokensNoSoft token budget; fit-to-budget reduces depth to fit.
collapseRolesNoSemantic-aware compression: collapse every node whose detected role (nav/hero/footer/sidebar/card/button) is in this list to a one-line `summary` instead of its full subtree — same `more` contract as depth truncation (call plumb_node on that node's `id` to expand it later). Opt-in and explicit on purpose: e.g. ['nav','footer'] to skip boilerplate chrome while keeping the hero and body in full.
Behavior5/5

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

Annotations already provide readOnly, openWorld, idempotent hints. Description adds significant behavior: deduplication, auto-layout resolved to flexbox, duplicate handling, expandAll with token budget, auto-trimming, and collapseRoles 'more' contract. Adds value beyond annotations.

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?

Single paragraph of 5 efficient sentences, front-loaded with main purpose. No wasted words, clear structure, easy to scan.

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 9 parameters and no output schema, description covers extraction behavior, paths, depth control, expandAll budget, collapseRoles, and output format. Sufficient for agent to understand and invoke correctly.

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 coverage is 100%, but description adds context for dual path usage and interplay between expandAll, depth, maxTokens. Explains collapseRoles semantics. Schema gives basics; description enriches understanding.

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 it extracts a Figma screen or node as a normalized PDS with deduplicated tokens and CSS-shaped node tree. It distinguishes between plugin and REST paths, differentiating it from siblings like plumb_outline or plumb_tokens.

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

Usage Guidelines4/5

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

Provides explicit guidance on when to use plugin path (with paired plugin) vs REST path (fileKey+id). Handles duplicate names with match list. Lacks direct comparison to other sibling tools for when to choose this over alternatives, but context is clear.

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