PicassoWeb

Capture hidden interactive UI

capture_interactions

Use this when important UI is hidden behind interactions and you do not yet know its selectors. Avoid it when you already know the target component or need continuous motion sampling.

Instructions

Use this when important UI is hidden behind interactions and you do not yet know its selectors. Avoid it when you already know the target component or need continuous motion sampling. Operate common triggers and capture menus, dialogs, tabs, accordions, and other revealed UI. Cost: heavy. 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: inspect_component, clone_section, capture_motion.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Absolute http:// or https:// URL to explore.
`settleMs`	No	Wait after each trigger for the revealed UI to settle.
`outputDir`	No	Absolute directory to save per-interaction screenshots 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.
`maxTriggers`	No	Maximum interactive triggers to operate.
`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.
`maxInlineScreenshots`	No	How many revealed-UI screenshots to return inline as images.

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": "capture_interactions",
+      "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: +{
+  "interactions": {
+    "items": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "metadata": {
+    "additionalProperties": {},
+    "properties": {
+      "analyzedAt": {
+        "type": "string"
+      },
+      "finalUrl": {
+        "type": "string"
+      },
+      "requestedUrl": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "requestedUrl",
+      "finalUrl",
+      "title",
+      "analyzedAt"
+    ],
+    "type": "object"
+  },
+  "triggersFound": {
+    "maximum": 9007199254740991,
+    "minimum": 0,
+    "type": "integer"
+  },
+  "warnings": {
+    "description": "Non-fatal limitations or incomplete evidence from this run.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}

addedOutput schema / properties / result / required

Added value: +[
+  "metadata",
+  "triggersFound",
+  "interactions",
+  "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.7/5.0

Behavior5/5

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

The description goes beyond the annotations by disclosing that the operation is cost-heavy, uses one browser page for one URL, and may write files when an output path is provided. This provides practical behavioral context about side effects and resource usage that 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 primary use case, followed by exclusions, cost, session constraints, and follow-ups. Every sentence contributes new, actionable information without repetition or 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 13 parameters, the description fairly covers what it does, when to use it, when to avoid it, cost implications, file-writing side effects, session constraints, and likely follow-ups. An output schema exists, so return-value details are already covered elsewhere.

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 13 parameters with meaningful descriptions. The tool description adds overall context but does not need to add parameter-level semantics because the schema fully covers that responsibility.

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 states a specific action and resource: capturing UI that is hidden behind interactions and whose selectors are unknown. It also names concrete UI types such as menus, dialogs, tabs, and accordions, and the sibling tool capture_motion is explicitly contrasted, making the tool's purpose unmistakable.

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 when-to-use rule ('when important UI is hidden behind interactions and you do not yet know its selectors'), an explicit when-not-to-use rule ('when you already know the target component or need continuous motion sampling'), and names follow-up alternatives like inspect_component, clone_section, and capture_motion.

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