Skip to main content
Glama
tathagat22

Plumb (plumb-mcp)

by tathagat22

Plumb · query

plumb_query
Read-onlyIdempotent

Query a Figma subtree by pattern—skeleton, buttons, text by font size, components, or semantic roles—instead of dumping the entire tree.

Instructions

Query a Figma subtree by pattern instead of dumping the whole tree. Use this on dense screens where plumb_node would be too big — pull a skeleton (structure only, no text/fills/effects), every button, every TEXT node above a size, every instance of a component, or every node Plumb classified with a given semantic role (nav/hero/footer/sidebar/card — select: "role"). Mirrors the same scope-resolution as plumb_node: pass id or name with the plugin paired, or fileKey + id (or a Figma URL) on the REST path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNode/screen id to query within.
maxNoMaximum font size for select: "text".
minNoMinimum font size for select: "text".
urlNoPaste a full Figma URL — fileKey and node-id auto-extracted.
nameNoScreen name — plugin path, resolved against the paired file.
roleNoRequired for select: "role" — which semantic role to match against the node's `pattern` field (the same field select:"buttons" reads).
selectYesQuery pattern. "skeleton" = structure-only (drops chars, fills, effects, vectorPath, text refs). "buttons" = nodes Plumb tagged with pattern: button (equivalent to select:"role", role:"button"; kept for backward compatibility). "text" = TEXT nodes, optionally filtered by font-size min/max. "components" = INSTANCE nodes, optionally filtered to a specific componentId. "role" = nodes carrying a given semantic role — see the `role` param.
fileKeyNoFigma file key — REST path. Omit when the plugin is paired.
componentIdNoFilter for select: "components" — return only instances of this component.
Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint, idempotentHint), description adds detail: what skeleton drops (chars, fills, effects), how buttons are tagged, that text filters by font-size, etc. No contradictions.

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 dense paragraph, front-loaded with purpose, no redundant sentences. Every sentence adds value: purpose, usage, examples, parameter clarification.

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?

Despite 9 params and no output schema, description covers all patterns, scoping options, parameter interdependencies, and use cases. Answers likely questions about when to use which select value and how to scope queries.

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?

Schema has 100% description coverage, but description adds context: explains 'select' enum options, clarifies 'role' is required for select:'role', and notes fileKey omission condition. Adds meaning beyond schema for each param.

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 states it queries a Figma subtree by pattern, not dumping the whole tree, and lists specific patterns (skeleton, buttons, text, components, role). It distinguishes from plumb_node by noting it's for dense screens where plumb_node would be too large.

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 says 'Use this on dense screens where plumb_node would be too big' and lists when each select pattern is appropriate (e.g., 'pull a skeleton', 'every button'). Also notes scope-resolution mirrors plumb_node.

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