PicassoWeb

Create a full replication kit

create_replication_kit

Build a complete page replication kit: captures screenshots, assets, layout trees, animations, and a guide for any URL in one pass.

Instructions

Use this when you need a broad first-pass package for reproducing a complete page. Avoid it when you only need one component, one screenshot, or a quick design overview. Write screenshots, assets, design data, layout trees, animations, and a replication guide in one pass. Cost: heavy. Session: captures one URL at multiple viewport states. May write files when an output path is provided. Replaces these separate first-pass calls: analyze_site, capture_screenshot, extract_assets, extract_layout. Possible follow-ups if evidence is still missing: extract_responsive, extract_animations, capture_motion, compare_replica.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Absolute http:// or https:// URL to build the kit for.
`maxAssets`	No	Maximum unique assets to download.
`outputDir`	Yes	Absolute directory to write the kit into.
`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.
`maxElements`	No	Maximum DOM elements to analyze.
`maxHeightPx`	No	Full-page screenshots taller than this are clipped.
`maxSvgBytes`	No	Skip inline SVGs larger than this.
`includeMobile`	No	Also capture a mobile-viewport screenshot and layout tree.
`viewportWidth`	No	Browser viewport width in CSS pixels.
`viewportHeight`	No	Browser viewport height in CSS pixels.
`maxBytesPerAsset`	No	Skip assets larger than this.
`allowPrivateNetwork`	No	Allow localhost and private-network URLs. Enable only for trusted sites.
`mobileViewportWidth`	No	Mobile capture width.
`mobileViewportHeight`	No	Mobile capture height.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Replication-kit paths and summary; the preview 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": "create_replication_kit",
+      "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: +"Replication-kit paths and summary; the preview is returned as MCP image content."

addedOutput schema / properties / result / properties

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

addedOutput schema / properties / result / required

Added value: +[
+  "metadata",
+  "outputDir",
+  "files",
+  "summary",
+  "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 communicate non-read-only and open-world behavior, and the description adds meaningful context by noting it may write files, is cost-heavy, and captures one URL at multiple viewport states. It does not detail overwrite behavior or auth requirements, but the annotations plus this description cover the essential safety and side-effect profile.

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 dense but every sentence earns its place: selection guidance, explicit exclusions, outputs, cost, side effects, replaced tools, and possible follow-ups. The most important usage guidance is front-loaded, and nothing feels redundant or wasted.

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 complex 18-parameter composite tool with an output schema, the description provides complete context: when to use it, when to avoid it, what it produces, what side effects it has, which siblings it replaces, and what to try next if evidence is missing. No critical selection or invocation context is absent.

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%, with all 18 parameters already well documented. The description adds a small amount of interpretive context, such as single-URL and multi-viewport behavior, but does not need to restate parameter details. This matches the baseline for full schema coverage.

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 defines the tool's purpose: creating a broad first-pass replication kit for a complete page, with an explicit list of outputs such as screenshots, assets, design data, layout trees, animations, and a replication guide. It also distinguishes this tool from narrower alternatives like single-component extraction or screenshot capture, so an agent can identify it without opening the schema.

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 explicit when-to-use guidance ('broad first-pass package for reproducing a complete page') and when-not-to-use guidance ('one component, one screenshot, or a quick design overview'). It also names the exact sibling tools this replaces and lists possible follow-up tools, leaving little to inference.

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