Skip to main content
Glama

Pagewatch

by dev.pagelens

read_page

Load a web page in a real browser and return its main content as clean markdown, with the title, canonical url and basic metadata. Handles javascript-rendered pages. Respects robots.txt and refuses sites that block automation rather than trying to defeat them. Pass api_key if you already have a pagewatch key, otherwise a free trial key is created for you on the first call and returned in the response.

    url: the page to read (http or https).
    api_key: an existing pagewatch bearer token, optional.
    wait_for_selector: css selector to wait for before reading, optional.
    scroll: scroll the page to trigger lazy-loaded content, optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
scrollNo
api_keyNo
wait_for_selectorNo

TDQS

A4.4/5.0
Behavior4/5

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

Discloses handling of JS rendering, robots.txt compliance, and free trial key creation. No annotations provided, but description adds safety and behavioral context. Could mention rate limits or failure handling.

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?

Well-structured with main purpose first, then handling details, then parameter list. Slightly verbose but no wasted 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?

Covers input parameters and output format (markdown with metadata). No output schema, but description suffices. Missing error scenarios, but adequate for a read 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?

With 0% schema coverage, description fully explains all four parameters: url, api_key, wait_for_selector, scroll. Adds meaning beyond schema types (e.g., wait_for_selector as CSS selector, scroll for lazy content).

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?

Clearly states it loads a web page and returns main content as clean markdown with metadata. Distinguishes from siblings like screenshot, pdf, balance.

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

Usage Guidelines4/5

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

Provides context: handles JavaScript-rendered pages, respects robots.txt, refuses blocked sites. Implicitly suggests use for dynamic content but lacks explicit when-not-to-use or alternatives.

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