PicassoWeb

Extract website layout tree

extract_layout

Read-onlyIdempotent

Use this when you specifically need structural geometry for a page or subtree. Avoid it when you need a full replication package or multiple viewport widths.

Instructions

Use this when you specifically need structural geometry for a page or subtree. Avoid it when you need a full replication package or multiple viewport widths. Return a bounded layout tree with sections, scroll containers, positioning, stacking, grid, and flex detail. Cost: standard. Session: uses one browser page for one URL. Does not write files. Possible follow-ups if evidence is still missing: inspect_component, extract_responsive.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Absolute http:// or https:// URL to analyze.
`maxDepth`	No	Maximum tree depth to descend.
`maxNodes`	No	Maximum nodes to include, consumed breadth-first.
`timeoutMs`	No	Navigation timeout in milliseconds.
`userAgent`	No	Optional browser user-agent override.
`waitUntil`	No	Page lifecycle event to await before extraction.	domcontentloaded
`autoScroll`	No	Scroll through the page before extraction to trigger lazy-rendered content.
`maxScrolls`	No	Maximum viewport-sized scroll steps when autoScroll is enabled.
`rootSelector`	No	Selector for the subtree root.	body
`viewportWidth`	No	Browser viewport width in CSS pixels.
`viewportHeight`	No	Browser viewport height in CSS pixels.
`allowPrivateNetwork`	No	Allow localhost and private-network URLs. Enable only for trusted sites.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes
`guidance`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed6 schema fields changedv0.10.1Aug 28, 2026

addedOutput schema / properties / guidance

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "cost": {
+      "enum": [
+        "light",
+        "standard",
+        "heavy"
+      ],
+      "type": "string"
+    },
+    "nextTools": {
+      "description": "Candidate follow-ups; do not call them automatically or in parallel.",
+      "items": {
+        "enum": [
+          "analyze_site",
+          "analyze_html",
+          "inspect_component",
+          "capture_screenshot",
+          "extract_assets",
+          "extract_animations",
+          "extract_layout",
+          "clone_section",
+          "capture_interactions",
+          "extract_responsive",
+          "compare_replica",
+          "create_replication_kit",
+          "capture_motion",
+          "crawl_site"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "sessionPolicy": {
+      "enum": [
+        "offline-document",
+        "single-url",
+        "multi-viewport",
+        "dual-page",
+        "site-crawl"
+      ],
+      "type": "string"
+    },
+    "summary": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "tool": {
+      "const": "extract_layout",
+      "type": "string"
+    },
+    "warnings": {
+      "description": "Non-fatal limitations or incomplete evidence from this run.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "writesFiles": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "tool",
+    "summary",
+    "nextTools",
+    "warnings",
+    "cost",
+    "writesFiles",
+    "sessionPolicy"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / result / additionalProperties
```
Added value: +{}
```

addedOutput schema / properties / result / properties

Added value: +{
+  "metadata": {
+    "additionalProperties": {},
+    "properties": {
+      "analyzedAt": {
+        "type": "string"
+      },
+      "finalUrl": {
+        "type": "string"
+      },
+      "requestedUrl": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "requestedUrl",
+      "finalUrl",
+      "title",
+      "analyzedAt"
+    ],
+    "type": "object"
+  },
+  "nodeCount": {
+    "maximum": 9007199254740991,
+    "minimum": 0,
+    "type": "integer"
+  },
+  "root": {
+    "anyOf": [
+      {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "truncated": {
+    "type": "boolean"
+  },
+  "warnings": {
+    "description": "Non-fatal limitations or incomplete evidence from this run.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}

addedOutput schema / properties / result / required

Added value: +[
+  "metadata",
+  "root",
+  "nodeCount",
+  "truncated",
+  "warnings"
+]

addedOutput schema / properties / result / type
```
Added value: +"object"
```

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "result",
+  "guidance"
+]

Changed1 schema field changedv0.10.0Aug 21, 2026

changedInput schema / properties / maxNodes / description

Previous value: -"Maximum nodes to include."New value: +"Maximum nodes to include, consumed breadth-first."

First observedv0.8.0Aug 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful context beyond these: it uses one browser page per URL, does not write files, has standard cost, and returns a bounded tree. There is no contradiction with the 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?

The description is compact and appropriately front-loaded: it opens with when to use, follows with when to avoid, then states output characteristics, cost, session usage, file behavior, and follow-ups. Every sentence contributes useful routing or behavioral information with no redundancy.

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?

For a 12-parameter tool with a rich input schema, an output schema, and safety annotations, the description covers the remaining decision-relevant context: when to choose it, what it returns at a high level, side effects (no writes, single page), cost class, and next steps. Nothing essential for correct invocation is missing.

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?

Schema description coverage is 100%, so the input schema already documents all 12 parameters thoroughly. The description adds little parameter-specific detail, but it reinforces the notion of a subtree (matching rootSelector) and bounded output (matching maxDepth/maxNodes), which is sufficient given the schema's completeness.

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 extracts structural geometry (a bounded layout tree with sections, scroll containers, positioning, stacking, grid, and flex detail) for a page or subtree. It explicitly contrasts this with full replication packages and multiple-viewport needs, distinguishing it from sibling tools like extract_responsive and create_replication_kit.

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?

It gives an explicit 'Use this when' condition and an 'Avoid it when' exclusion, naming the exact scenarios that should route elsewhere (full replication package, multiple viewport widths). It also lists concrete follow-up tools (inspect_component, extract_responsive) when evidence is still missing.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/blackridder22/PicassoWeb'

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