Skip to main content
Glama
Edge DevTools MCP

Edge DevTools MCP

by syunnrai123

edge_screenshot

Captures a screenshot of the current Edge browser page as PNG or JPEG, with optional JPEG quality control for visual inspection and debugging.

Instructions

截取页面截图

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": "edge_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo截图格式png
qualityNoJPEG质量(1-100)
sessionIdNo会话ID(可选)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and discloses almost nothing: not whether the operation is read-only, whether it needs an attached session or active page, how the image is delivered (inline data, file path, or temp location), or whether it times out on large pages. For an action tool with zero annotation coverage this is a substantial gap.

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 short sentence with no filler and the action front-loaded. It is efficient, though its brevity borders on under-specification rather than being a model of tightness.

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?

There is no output schema, so the description should explain what the caller receives (image bytes, URL, or saved path) and whether a session or page target is required. With three parameters, one optional session binding, and no annotations, a six-character description leaves the agent guessing on the key outcome of the call.

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% and every parameter (format, quality, sessionId) already carries its own Chinese description, so the description adds no meaning beyond the schema. The default-3 baseline applies when the schema does the heavy lifting.

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?

The description states a specific verb plus resource ("截取页面截图" = capture page screenshot), so the agent can tell it apart from sibling tools like edge_get_page_content or edge_navigate. It is clear but offers no explicit differentiation from those siblings, which keeps it below a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to use this instead of edge_get_page_content or edge_evaluate, nor any prerequisite such as requiring an active session or connected browser. The agent must infer context entirely from the sibling names.

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