Skip to main content
Glama
sethbang

MCP Screenshot Server

by sethbang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

take_screenshot

Capture web pages or specific elements using a headless browser. Screenshots save to a configurable output folder.

Instructions

Capture web page or element via headless browser. Saves to ~/Documents/screenshots by default (configurable via SCREENSHOT_OUTPUT_DIR env var).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to capture
widthNoViewport width
heightNoViewport height
fullPageNoCapture full page
selectorNoCSS selector for element
waitForSelectorNoWait for selector
waitForTimeoutNoDelay in ms
outputPathNoAbsolute path, or relative to home dir

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / fullPage / description
      Previous value: -"Capture full scrollable page"New value: +"Capture full page"
    • changedInput schema / properties / height / description
      Previous value: -"Viewport height in pixels"New value: +"Viewport height"
    • changedInput schema / properties / outputPath / description
      Previous value: -"Custom output path (optional)"New value: +"Absolute path, or relative to home dir"
    • addedInput schema / properties / selector
      Added value: +{
+  "description": "CSS selector for element",
+  "type": "string"
+}
    • changedInput schema / properties / url / description
      Previous value: -"URL to capture (can be http://, https://, or file:///)"New value: +"URL to capture"
    • addedInput schema / properties / waitForSelector
      Added value: +{
+  "description": "Wait for selector",
+  "type": "string"
+}
    • addedInput schema / properties / waitForTimeout
      Added value: +{
+  "description": "Delay in ms",
+  "maximum": 30000,
+  "minimum": 0,
+  "type": "number"
+}
    • changedInput schema / properties / width / description
      Previous value: -"Viewport width in pixels"New value: +"Viewport width"
  2. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only mentions method and save location; it omits critical behavioral traits like destructiveness, permission needs, or return value.

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?

Two concise sentences: first states purpose, second details save behavior. Front-loaded and no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 8 parameters and no output schema, the description omits return value, error handling, and other essential context, leaving significant gaps.

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 covers all 8 parameters with descriptions, so baseline is 3. The description adds the default save path and env var override, providing marginal extra context.

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 uses specific verb 'capture' and resource 'web page or element' with method 'via headless browser', clearly distinguishing it from sibling 'take_system_screenshot' which captures system screens.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for web screenshots but does not explicitly state when to use versus alternatives, nor does it mention prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools