Handiworks

Render URL to screenshot or PDF

render

Render a web page to a PNG/JPEG screenshot or a PDF using a real headless browser. Returns the image inline (base64) or the PDF as an embedded resource. Results are cached for 24h.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	The absolute URL to render (must include https:// or http://).
`fresh`	No	Bypass the 24h cache and force a fresh render.
`width`	No	Viewport width in pixels.
`format`	No	Output format. png/jpeg return an image; pdf returns a PDF document.	png
`height`	No	Viewport height in pixels.
`fullPage`	No	For screenshots: capture the entire scrollable page instead of just the viewport.
`pdfFormat`	No	Paper size, used only when format is pdf.	A4
`waitUntil`	No	Navigation completion signal before capturing.	networkidle2

Schema Changelog

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

First observedJul 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Discloses key behaviors: uses real headless browser, returns inline base64 or embedded resource, and 24-hour caching. Does not mention error handling, rate limits, or authorization needs, but covers major operational aspects.

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?

Two sentences, front-loaded with action and output. Every sentence adds value. No redundant information.

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?

With 8 parameters and no output schema, description provides return format (base64/embedded) and caching. Could mention error conditions or typical response size, but sufficient for most use cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each parameter already has a description. The tool description adds only general context (caching, output format) without enhancing specific parameter meaning. Meets baseline.

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?

Description clearly states rendering a web page to screenshot or PDF, using a headless browser. It distinguishes from siblings 'check_link' and 'convert' by focusing on visual capture rather than link checking or format conversion.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., 'check_link' for link validation, 'convert' for format transformation). The description implies usage for capturing web page visuals, but lacks exclusion criteria.

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

All Handiworks tools Inspect

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.1/5.0

Disambiguation5/5

Each tool serves a distinct purpose: check_link checks URL health, convert transforms content formats, render creates screenshots/PDFs. No overlap in functionality.

Naming Consistency4/5

Two tools use verb_noun pattern (check_link, render) while one is a single verb (convert). Mostly consistent but minor deviation.

Tool Count3/5

With only 3 tools, the server is small but usable. It covers basic web utilities, though additional tools like extract_text could enhance scope.

Completeness4/5

The tool set covers link checking, format conversion, and web rendering. No obvious dead ends for these operations, though some related tasks (e.g., validate HTML) are absent.

Resources

Need Help?