Skip to main content
Glama

Pagewatch

by dev.pagelens

screenshot

Take a screenshot of a web page rendered in a real browser and return it as base64 image data (png by default, jpeg optional), with the final url and pixel size. Consent overlays are hidden so the shot shows the page. Respects robots.txt. Pass api_key if you have a pagewatch key, otherwise a free trial key is created for you and returned.

    url: the page to capture.
    api_key: an existing pagewatch bearer token, optional.
    full_page: capture the entire scrollable page, not just the viewport.
    width, height: viewport size in pixels.
    format: png or jpeg.
    wait_for_selector: css selector to wait for before capturing, optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
widthNo
formatNopng
heightNo
api_keyNo
full_pageNo
wait_for_selectorNo

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description covers key behaviors: uses a real browser, hides consent overlays, respects robots.txt, handles API keys. However, it lacks details on error handling, loading behavior, timeouts, and what happens for invalid URLs.

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 structured with a clear opening sentence and bullet-like parameter explanations. It is efficient but could be slightly more concise by avoiding repetition of 'base64 image data' in the first and subsequent sentences.

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

Completeness4/5

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

Given 7 parameters, no annotations, and no output schema, the description covers return format, consent handling, and API key behavior. Minor gaps include error handling and rate limits, but overall it is fairly complete for a screenshot 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?

Despite 0% schema coverage, the description explains each parameter (url, api_key, full_page, width, height, format, wait_for_selector) with meaningful context, such as api_key creating a free trial key. It adds value beyond the schema's type-only definitions.

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 it takes a screenshot of a web page and returns base64 image data, with specific details about format and output. It distinguishes from siblings like pdf (conversion) and read_page (text extraction) by being the only visual capture tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for visual page capture but does not explicitly state when to use this tool vs alternatives (e.g., read_page for text, pdf for PDFs). It mentions consent overlay hiding and robots.txt respect, but no clear guidance on exclusions or when not to use.

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

All Pagewatch toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool has a distinct purpose: balance checks credits, pdf converts pages to PDF, read_page extracts markdown, register creates API keys, and screenshot captures images. No overlapping functionality.

Naming Consistency4/5

Tool names are lowercase and descriptive, with 'read_page' using an underscore while others are single words. This minor inconsistency is easy to overlook but prevents a perfect score.

Tool Count5/5

Five tools cover the core needs of a web page tool: key management (balance, register), content extraction (read_page), and output formats (pdf, screenshot). The count is well-scoped for its purpose.

Completeness4/5

The tool set covers key lifecycle and primary page actions. A minor gap is the lack of a tool to delete or manage keys, but balance and register provide sufficient functionality.

Resources