Skip to main content
Glama
gaforov

selenium-mcp

by gaforov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

take_screenshot

Capture a PNG screenshot of the visible viewport to verify visual layout or show a user a step. Save to disk or return as base64.

Instructions

Capture a PNG screenshot of the visible viewport. Returns it as base64 and/or saves it to savePath (folders are created as needed; an existing file is overwritten). Use it when visual layout or appearance matters, or to show the user a step. To check text or state, prefer capture_page, get_text, or the assert tools: they are exact and much smaller than an image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
savePathNoAbsolute path to write the PNG to, e.g. '/home/me/shots/login.png' or 'C:/shots/login.png'. Omit to not save.
includeBase64NoInclude the PNG as base64 in the result (default true). Set false when saving to disk to keep the response small.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • addedInput schema / properties / includeBase64 / description
      Added value: +"Include the PNG as base64 in the result (default true). Set false when saving to disk to keep the response small."
    • addedInput schema / properties / savePath / description
      Added value: +"Absolute path to write the PNG to, e.g. '/home/me/shots/login.png' or 'C:/shots/login.png'. Omit to not save."
  2. First observedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return format (base64 and/or disk), that folders are created as needed, and that an existing file is overwritten – a clear destructive-on-disk side effect. It omits any note on permissions or capture timing, but the important behavioral traits are covered.

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?

Three sentences, all front-loaded: purpose first, then behavior/side effects, then the routing guidance. Every sentence earns its place and nothing is redundant.

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?

Complete for a screenshot tool with no output schema: the description explains both the returned payload (base64) and the disk-write behavior, and gives clear routing relative to the many sibling read/inspect tools. Nothing needed to call it correctly is missing.

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 coverage is 100%, and both parameters are fully documented in the schema, including the savePath example paths and the includeBase64 default. The description reinforces the base64/savePath duality but adds no syntax or format detail beyond the schema, so the baseline 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?

States a specific verb and resource ('Capture a PNG screenshot of the visible viewport'), including the scope ('visible viewport') that distinguishes it from a full-page capture. It also names the sibling capture_page and the text-based alternatives, so an agent can route between them without opening a schema.

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?

Explicit when-to-use ('when visual layout or appearance matters, or to show the user a step') and explicit when-not with named alternatives ('To check text or state, prefer capture_page, get_text, or the assert tools'). The exclusion criterion ('exact and much smaller than an image') gives a concrete decision rule.

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