Skip to main content
Glama
tathagat22

Plumb (plumb-mcp)

by tathagat22

Plumb · import web

plumb_import_web
Read-only

Import a live webpage's visible DOM structure and semantics, mapping it onto a semantic design graph with real CSS values and detected roles. Use to audit site structure or track changes over time with multi-viewport support.

Instructions

Import a live webpage's structure and semantics — no Figma connection needed. Drives headless Chrome to walk the page's visible DOM (skipping script/style/hidden elements), maps it onto the same Semantic Graph Figma designs use, and returns nodes carrying real CSS values (hex colors, literal px) plus a detected role (nav/hero/footer/sidebar) using the exact same classifier plumb_node's pattern field uses. Use this to understand an existing site's structure, audit it (plumb_audit accepts this shape too), or track it over time (plumb_diff two imports of the same URL). Text nodes also carry fontFamily, and the result carries fontLinks URLs for every captured family that matches a known Google Fonts family — so generated code doesn't silently fall back to a system font. Pass viewports to capture the SAME page at multiple sizes in one call (e.g. mobile + desktop) — a real responsive layout (a hamburger nav under 768px, a grid that collapses to one column) is invisible to a single fixed-size capture.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe page URL to import.
selectorNoCSS selector to root the walk at — omit to walk from document.body.
viewportsNoCapture the same page at multiple sizes in one call. Pass `true` for the default set (mobile 390×844, tablet 768×1024, desktop 1440×900), or an explicit array of {label, width, height}. Omit for today's single desktop capture (unchanged). Returns `{ url, viewports: { <label>: <WebSpecDocument> } }` instead of a single flat document when used.
Behavior4/5

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

Description adds beyond annotations: drives headless Chrome, skips hidden elements, returns real CSS values and fontLinks. Annotations already declare readOnlyHint=true, so no contradiction. OpenWorldHint=true aligns with external webpage dependency.

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?

Description is dense but well-structured, front-loaded with purpose. Could be slightly trimmed (e.g., fontFamily detail), but every sentence adds value. Appropriate length for a complex import tool.

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 explains return format for viewports and mentions fontLinks. Covers all params and use cases. Adequate for a tool with 3 params and rich behavior.

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%, giving baseline 3. Description adds significant value for 'viewports' (explains true as default set, result shape) and 'selector'. Provides context beyond schema descriptions.

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?

The description clearly states the tool imports a live webpage's structure and semantics into a Semantic Graph, using specific verbs and resource (import web). It distinguishes from sibling tools like plumb_node and plumb_audit.

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 states when to use (understand site structure, audit, track over time) and provides alternatives (plumb_audit, plumb_diff). Mentions that no Figma connection is needed, clarifying a non-use case.

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