Skip to main content
Glama

Pagewatch

by dev.pagelens

pdf

Render a web page (by url) or raw html into a pdf and return it as base64 pdf data. Provide exactly one of url or html. Respects robots.txt for url input. Pass api_key if you have a pagewatch key, otherwise a free trial key is created for you and returned.

    url: the page to convert, optional.
    html: raw html to convert, optional (provide url or html, not both).
    api_key: an existing pagewatch bearer token, optional.
    paper: A4, Letter, Legal or A3.
    landscape: landscape orientation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
htmlNo
paperNoLetter
api_keyNo
landscapeNo

TDQS

B3.4/5.0
Behavior3/5

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

Mentions respecting robots.txt and api_key creation behavior. No annotations provided, so description carries burden; could disclose more like idempotency or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two paragraphs; first is concise, second repeats parameter info. Slightly verbose but not excessive.

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?

Covers main functionality, but lacks output format details (base64 string specifics), error handling, or size limits. Adequate for 5-param tool with no output schema.

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?

Schema coverage is 0%, but description adds meaning: explains mutual exclusivity, lists paper sizes, landscape orientation, and api_key purpose. Compensates well for missing schema descriptions.

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 renders a URL or HTML into a PDF and returns base64 data. It distinguishes the core function but does not explicitly differentiate from sibling tools like screenshot or read_page.

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?

Provides guidance on mutual exclusivity of url/html and api_key handling, but lacks when-to-use vs. alternatives (e.g., when to use pdf instead of screenshot).

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