Skip to main content
Glama

screenshot

Capture screenshots of the active browser tab with support for full-page stitching, region clipping, and format selection. Options include base64 encoding for vision models and automatic resizing to avoid dimension limits.

Instructions

Screenshot active tab. Saves to ~/.mcp-stealth/screenshots/.

Args:
    filename: output name (default timestamped)
    full_page: stitch entire page height (slower, larger file)
    return_base64: append base64 body to response (useful for vision models)
    format: "auto" (from extension, default), "png" (lossless), or "jpeg" (smaller)
    quality: JPEG quality 1-100 (default 80) — ignored for PNG
    region: clip to {x, y, width, height} — uses CDP Page.captureScreenshot clip
            (skips full-viewport paint, 2-5× faster for small crops)
    max_dimension: if either width or height exceeds this (px), the image is
        resized proportionally via OpenCV INTER_AREA. Default 1920 keeps output
        under the 2000 px per-side limit that LLM image tools (Claude/GPT) enforce
        — prevents "image exceeds dimension limit" failures on long full_page
        captures or hi-DPR device emulation. Pass 0 to disable resizing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameNo
full_pageNo
return_base64No
formatNoauto
qualityNo
regionNo
max_dimensionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It explains file saving location, parameter behaviors (e.g., full_page slower, region faster, max_dimension prevents LLM errors). Missing edge cases like failure handling (e.g., no active tab) but still strong.

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?

The description is well-structured with a summary followed by parameter explanations. It is slightly lengthy but every sentence provides useful information. Could be more concise by removing redundant phrasing.

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

Completeness3/5

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

Given 7 parameters and presence of an output schema, the description covers parameter behavior well but misses some context: no mention of prerequisites (e.g., active browser tab), potential failures, or permission requirements. Adequate but not fully comprehensive.

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

Parameters5/5

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

Schema description coverage is 0%, but the description thoroughly explains each parameter with practical details (e.g., default timestamped, JPEG quality impact, OpenCV resizing for max_dimension). Adds significant value beyond the raw schema.

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 clearly states the tool's purpose ('Screenshot active tab') and details parameters. However, it does not distinguish from siblings like 'browser_snapshot' or 'save_pdf', which could cause confusion.

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?

No explicit guidance on when to use this tool vs alternatives. It is implied for capturing screenshots, but does not specify prerequisites, limitations, or when to choose other tools.

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/RobithYusuf/mcp-stealth-chrome'

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