Skip to main content
Glama
blackridder22

PicassoWeb

by blackridder22
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Capture website screenshot

capture_screenshot
Idempotent

Use this when you only need visual evidence or a reference image of a page or element. Avoid it when you need the full implementation package; create_replication_kit already includes screenshots.

Instructions

Use this when you only need visual evidence or a reference image of a page or element. Avoid it when you need the full implementation package; create_replication_kit already includes screenshots. Capture a viewport, full page, or selected element as an image the agent can inspect. Cost: light. 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, compare_replica.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAbsolute http:// or https:// URL to capture.
modeNoWhat to capture.viewport
selectorNoCSS selector, required when mode is 'element'.
timeoutMsNoNavigation timeout in milliseconds.
userAgentNoOptional browser user-agent override.
waitUntilNoPage lifecycle event to await before extraction.domcontentloaded
autoScrollNoScroll through the page before extraction to trigger lazy-rendered content.
maxScrollsNoMaximum viewport-sized scroll steps when autoScroll is enabled.
outputPathNoAbsolute file path to also save the image to.
maxHeightPxNoFull-page captures taller than this are clipped.
viewportWidthNoBrowser viewport width in CSS pixels.
viewportHeightNoBrowser viewport height in CSS pixels.
allowPrivateNetworkNoAllow localhost and private-network URLs. Enable only for trusted sites.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesScreenshot metadata; binary data is returned as MCP image content.
guidanceYes

Schema Changelog

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

  1. Changed7 schema fields changedv0.10.1
    • 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_screenshot",
+      "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: +"Screenshot metadata; binary data is returned as MCP image content."
    • addedOutput schema / properties / result / properties
      Added value: +{
+  "bytes": {
+    "maximum": 9007199254740991,
+    "minimum": 0,
+    "type": "integer"
+  },
+  "metadata": {
+    "additionalProperties": {},
+    "properties": {
+      "analyzedAt": {
+        "type": "string"
+      },
+      "finalUrl": {
+        "type": "string"
+      },
+      "requestedUrl": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "requestedUrl",
+      "finalUrl",
+      "title",
+      "analyzedAt"
+    ],
+    "type": "object"
+  },
+  "mimeType": {
+    "type": "string"
+  },
+  "mode": {
+    "enum": [
+      "viewport",
+      "fullPage",
+      "element"
+    ],
+    "type": "string"
+  },
+  "savedPath": {
+    "type": "string"
+  },
+  "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",
+  "mode",
+  "mimeType",
+  "bytes",
+  "warnings"
+]
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "result",
+  "guidance"
+]
  2. First observedv0.8.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context beyond that: cost level, one browser page per URL, and the fact that files may be written when an output path is provided. It does not contradict the annotations and provides enough extra operational context.

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 guidance (when to use vs. avoid). The cost, session, and follow-up statements are each useful and do not waste words. It is structured so an agent can quickly parse selection criteria before invocation details.

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?

Given the rich input schema and the presence of an output schema, the description covers all the essential decision-making context: intended use, exclusions, side effects, resource usage, and follow-up alternatives. An agent has enough information to select and invoke this tool correctly without guessing.

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 fully documents all 13 parameters. The description mentions capture modes and file output, but those are already reflected in the schema. It adds no meaningfully new parameter information, so the baseline score of 3 is appropriate.

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 concrete action and resource: capture a website screenshot as visual evidence or reference image. It also distinguishes the tool from create_replication_kit, which is a key sibling differentiator. This is far beyond a vague restatement of the tool name.

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 explicitly says when to use the tool ('when you only need visual evidence or a reference image') and when to avoid it ('when you need the full implementation package; create_replication_kit already includes screenshots'). It also suggests possible follow-ups when evidence is still missing, which helps an agent decide among siblings.

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

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