Skip to main content
Glama
Dutta-SD

web-fetch-mcp

by Dutta-SD

screenshot

Read-only

Capture a full-page or viewport screenshot of any web page using a real browser. Handles anti-bot protections and overlays automatically.

Instructions

Render a web page in a real browser and return a PNG screenshot.

The visual counterpart to fetch. Use it when the user asks to "show", "screenshot", or "see what a page looks like", or when layout/visual state matters (charts, dashboards, rendered design). Same anti-bot-resistant real Chrome engine as fetch's Tier 2, with optional proxy support.

Args: url: Fully-qualified URL (https://...). full_page: True (default) captures the entire scrollable page; False captures only the viewport. viewport_width: Browser viewport width in pixels. Default 1920. viewport_height: Browser viewport height in pixels. Default 1080. wait_ms: Extra settle time (ms) after load before capturing. Default 2000. dismiss_selector: CSS/text selector for a blocking overlay to click before capturing (cookie banner, modal). Failures are silent. proxy: Optional proxy URL "http[s]://[user:pass@]host:port" (ideally residential) for the IP-reputation layer.

Returns: The screenshot as an MCP Image (PNG), shown inline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
full_pageNo
viewport_widthNo
viewport_heightNo
wait_msNo
dismiss_selectorNo
proxyNo
Behavior5/5

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

Describes real Chrome engine, optional proxy, full page vs viewport, wait time, dismiss selector. No contradiction with readOnlyHint annotation.

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?

Well-structured with one sentence purpose, usage guidance, then arg list with clear descriptions. No fluff.

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?

Covers all parameters, return type, and usage context. No output schema but explains return as MCP Image inline. Adequate for 7-param tool.

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?

Despite 0% schema description coverage, the description explains all 7 parameters in detail, including defaults, behavior, and constraints (e.g., proxy format).

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?

Clear verb 'Render' + resource 'web page' + output 'PNG screenshot'. Distinguishes from sibling 'fetch' by being visual counterpart. Explicit usage cues.

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?

States when to use: user asks to show/screenshot, visual state matters. Explicitly compares to fetch and mentions proxy support for anti-bot scenarios.

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/Dutta-SD/web-fetch-mcp'

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