Skip to main content
Glama

web_screenshot

Read-only

Capture a PNG screenshot of a web page to show its layout and design, and cross-check the rendered pixels against the page's text from the same browser visit.

Instructions

A PNG screenshot of a web page. The fourth tool of the module.

WHEN TO CALL. You need to SHOW a page to a person — the layout, the design, what the text does not carry. And you need to CROSS-CHECK: the shot and the text are obtained in one browser visit but by different routes — the pixels are drawn by the layout engine, the text comes from the DOM. A disagreement between them catches what neither route sees alone.

WHEN NOT TO CALL. You need the text of the page — that is web_read, many times cheaper. A screenshot costs a browser launch.

WHAT IT RETURNS. png_base64 — the shot itself; bytes — its size; page_text — the text of THE SAME visit, up to max_chars; page_text_chars — the length of the whole text, which may be greater; page_text_truncated; browser_version.

HOW TO READ THE ANSWER — two things, and they are DIFFERENT.

  1. shot_taken — THE SHOT WAS TAKEN: the browser is alive, the page loaded.

  2. expected_found — WHAT WE EXPECTED IS ON THE PAGE (when expect was given). A shot can be taken flawlessly and show the wrong thing: a stub, a captcha, an error page. Do not confuse these two fields — a page that honestly failed a check and a browser that never opened are different events.

A signal worth seeing: there is a shot and page_text_chars is near zero — the page drew, and has nothing to say.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesthe page address
expectNomarkers that must be present on the page. They are checked against the TEXT of the same visit: a screenshot cannot check itself. Not found gives expected_found=false, and the shot is still taken
full_pageNofalse by default — the visible area. true captures the whole page and costs more
max_charsNohow much of the page text to return beside the shot; 2000 by default. The text is here to be compared with the picture — for the whole document call web_read, which has a cursor

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.2.1

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses return fields (png_base64, bytes, page_text, page_text_chars, page_text_truncated, browser_version) and explains the distinction between shot_taken and expected_found, including that a shot is still taken even if expected markers are absent. It also warns about cost (browser launch) and the behavior of page_text truncation. No contradiction with annotations (readOnlyHint, etc.).

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 clear sections and a front-loaded purpose statement. It is slightly verbose due to stylistic capitalization and dramatic phrasing, but every section serves a purpose and adds information without bloat.

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?

The description covers the output fields, the meaning of key result flags, edge cases (captcha, error pages), the signal of near-zero page_text_chars, and cost considerations. It even points to an alternative tool for full text retrieval, making it complete for an agent deciding to call this 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?

All four parameters have detailed schema descriptions that go beyond simple types: expect explains the check is against text and that a miss still yields a shot; full_page notes cost implications; max_chars explains the default and points to web_read for full documents. The description adds value to the schema by linking parameters to the tool's purpose.

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 clearly states 'A PNG screenshot of a web page' and contrasts with web_read for text. It explicitly names the resource (web page) and the action (screenshot), and distinguishes it from sibling tools.

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 'WHEN TO CALL' and 'WHEN NOT TO CALL' sections explicitly specify when to use the tool (to show layout/design, to cross-check visuals with text) and when not to (when only text is needed, use web_read). This provides direct, unambiguous guidance relative to alternatives.

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

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/AG-Bureau/mcp-search'

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