Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

screenshot

Read-only

Capture a PNG or JPEG of a page target, optionally clipping to a CSS selector's element bounds for focused visual debugging.

Instructions

Capture a PNG/JPEG screenshot of a page target via Page.captureScreenshot (optional CSS selector clips to element bounds)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo
qualityNo
selectorNoOptional CSS selector — capture only that element's bounding box
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true is consistent with a capture operation, and the description usefully reveals the underlying mechanism (Page.captureScreenshot) and that selector clips to element bounds. It does not disclose the single most important behavioral trait for this tool: whether the image is returned inline (and in what form) or written to a file — especially relevant given the save_screenshot sibling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the key action first and the selector behavior in a parenthetical — no waste. Slightly dense with jargon ("page target", "Page.captureScreenshot") but structurally sound.

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?

With five parameters, 40% schema coverage, and no output schema, the description should explain the return value (image payload vs. saved artifact) and targeting semantics. It omits both, which leaves meaningful gaps for a tool whose output shape is the main ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40%, so the description needs to compensate, but it mostly repeats the schema's own selector text. It says nothing about quality (presumably JPEG quality), what targetId means versus processId, or how format interacts with quality, leaving two enumerated/unbounded params with no interpretive guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Capture a PNG/JPEG screenshot of a page target") and even names the underlying CDP method, so the agent knows exactly what the tool does. It does not, however, distinguish itself from siblings like save_screenshot or diff_screenshot, leaving the agent to infer the difference from names alone.

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?

Usage is only implied by the purpose: capture a page screenshot. There is no explicit when-to-use vs when-not, no mention that save_screenshot should be preferred when persisting to disk, and no prerequisites (e.g. an attached page or running app) are stated.

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