PicassoWeb

Clone a website section

clone_section

Use this when you need a portable implementation package for one known section. Avoid it when you need an entire page; use create_replication_kit.

Instructions

Use this when you need a portable implementation package for one known section. Avoid it when you need an entire page; use create_replication_kit. Return cleaned HTML, scoped CSS, dependencies, assets, and an optional screenshot for one section. Cost: standard. Session: uses one browser page for one URL. May write files when an output path is provided. Possible follow-ups if evidence is still missing: capture_motion, compare_replica.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Absolute http:// or https:// URL to clone from.
`selector`	Yes	CSS selector for the section to clone.
`maxAssets`	No	Maximum assets to download when outputDir is set.
`outputDir`	No	Absolute directory to download the section's assets into (URLs are rewritten to relative paths).
`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.
`viewportWidth`	No	Browser viewport width in CSS pixels.
`viewportHeight`	No	Browser viewport height in CSS pixels.
`maxBytesPerAsset`	No	Skip assets larger than this.
`includeScreenshot`	No	Include a screenshot of the cloned section.
`allowPrivateNetwork`	No	Allow localhost and private-network URLs. Enable only for trusted sites.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Portable section package; any screenshot is returned as MCP image content.
`guidance`	Yes

Schema Changelog

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

Changed7 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": "clone_section",
+      "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 / description

Added value: +"Portable section package; any screenshot is returned as MCP image content."

addedOutput schema / properties / result / properties

Added value: +{
+  "assetRefs": {
+    "items": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "assets": {
+    "items": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "css": {
+    "type": "string"
+  },
+  "html": {
+    "type": "string"
+  },
+  "metadata": {
+    "additionalProperties": {},
+    "properties": {
+      "analyzedAt": {
+        "type": "string"
+      },
+      "finalUrl": {
+        "type": "string"
+      },
+      "requestedUrl": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "requestedUrl",
+      "finalUrl",
+      "title",
+      "analyzedAt"
+    ],
+    "type": "object"
+  },
+  "selector": {
+    "type": "string"
+  },
+  "warnings": {
+    "description": "Non-fatal limitations or incomplete evidence from this run.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}

addedOutput schema / properties / result / required

Added value: +[
+  "metadata",
+  "selector",
+  "html",
+  "css",
+  "assets",
+  "assetRefs",
+  "warnings"
+]

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

changedOutput schema / required

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

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 indicate the tool is not read-only, and the description adds concrete behavioral detail beyond that: 'May write files when an output path is provided,' 'uses one browser page for one URL,' and 'Cost: standard.' This gives the agent useful cost and side-effect context that the annotations alone do not convey.

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 front-loaded with the most important decision info: use case, exclusions, return contents, cost, session constraints, and follow-ups. Every sentence contributes actionable guidance with no filler.

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 tool with 14 parameters, the description covers scope, return artifacts, side effects, cost, session behavior, and follow-up tools, while the output schema and 100% parameter coverage handle the remaining details. Nothing essential to 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 schema already documents all 14 parameters. The description mentions 'an optional screenshot' and 'output path,' which lightly reinforce two parameters, but it does not need to add much parameter-level detail 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 names a specific verb and resource: producing a 'portable implementation package for one known section.' It explicitly contrasts with create_replication_kit for entire pages, which makes the tool's scope immediately distinguishable from a sibling.

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?

The description gives direct when-to-use guidance ('when you need a portable implementation package for one known section') and an explicit when-not-to-use instruction with a named alternative ('Avoid it when you need an entire page; use create_replication_kit'). It also suggests relevant follow-up tools, giving an agent a clear decision path.

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