Skip to main content
Glama
andresolbach

nodriver-mcp-server

Take screenshot

take_screenshot
Read-only

Capture the page, viewport, or a single element as an image to verify layout, compare visual changes, or extract text that exists only inside images.

Instructions

Capture the page, the viewport or a single element as an image.

Do NOT use this to read a page. take_snapshot gives you the same content as searchable text, is dramatically smaller, and yields the uids every interaction tool needs. Use a screenshot only when you genuinely need pixels: layout and styling checks, visual regression, or text that exists only inside an image.

Element capture needs a uid from the current snapshot. Without file_path the image is returned inline as a base64 data URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidNoCapture just this element, using a uid from the most recent take_snapshot. Cannot be combined with full_page. Empty string captures the page.
formatNoImage format. "png" is lossless and the default; "jpeg" or "webp" with a quality setting are far smaller, which matters for full-page captures.png
qualityNoCompression quality from 1 to 100, for jpeg and webp only. Ignored for png. 0 leaves Chrome's default.
file_pathNoWrite the image to this local path. Omit to get a base64 data URL inline in the response — that is expensive, so prefer a file for full-page or high-DPR captures.
full_pageNoCapture the whole scrollable page rather than just the visible viewport. Cannot be combined with `uid`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful context: the expensive inline base64 data URL behavior, the dependency on a snapshot uid for element capture, and performance trade-offs (file vs inline). This enriches the annotation baseline significantly.

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 three paragraphs but every sentence earns its place. It front-loads the core purpose, then provides critical usage warnings, alternatives, and dependencies. No filler or redundant content beyond reinforcing valuable guidance.

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?

With an output schema present and 5 parameters fully documented, the description covers selection criteria, alternatives, output behavior, and performance considerations. It is complete for an agent to correctly decide when and how to invoke this tool.

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

Parameters4/5

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

Schema coverage is 100% with detailed parameter descriptions. The description adds extra clarity about the uid requirement for element capture, reiterates cost implications of omitting file_path, and clarifies the distinction among page/viewport/full_page. While schema already covers most, this supplements with usage 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 specifies the exact action: capture the page, viewport, or element as an image. It explicitly differentiates from take_snapshot by stating when screenshots are needed (pixels, layout, styling) versus when text extraction is appropriate.

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?

The description gives strong when-to-use and when-not-to-use guidance, naming take_snapshot as the alternative for reading text and explaining that screenshots should only be used for visual needs. It also notes the requirement of a uid for element capture and the inline base64 behavior without file_path.

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/andresolbach/nodriver-mcp-server'

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