Capture full-page screenshots and PDFs from any URL. Chromium rendering, custom viewport, PNG/JPEG/WebP output.
Two tools with complete input schemas and detailed descriptions. Both tools have clear verb-noun naming (capture_screenshot, webpage_to_pdf) and comprehensive parameter documentation with enums and defaults. Descriptions are well-structured (200+ chars) with use-case guidance and anti-patterns. However, output schemas are not formally documented in the source code, only described in prose. No error handling guidance or recovery patterns visible. Tool composition is sound (separate concerns), but no pagination or batch variants.
Use this when you need a visual capture of a web page. Renders in a real Chromium browser and returns an image. Returns: 1. Binary image (PNG, JPEG, or WebP) 2. Custom viewport support (width/height in px) 3. Full-page scroll capture option 4. Configurable format and quality. Example output: binary image file with Content-Type image/png, typical size 200-800KB for a full page. Use this BEFORE visual QA testing, generating page thumbnails, archiving web pages, or verifying responsive design. Essential for automated screenshot pipelines and visual regression testing. Do NOT use for text extraction -- use web_scrape_to_markdown instead. Do NOT use for PDF from data -- use document_generate_pdf instead. Do NOT use for PDF from URL -- use webpage_to_pdf instead.
Use this when you need to convert a live web page to a printable PDF document. Renders in a real Chromium browser and returns binary PDF. Returns: 1. Binary PDF file 2. Configurable paper format (A4, Letter, Legal, Tabloid) 3. Print-optimized layout with proper page breaks. Example output: binary PDF file with Content-Type application/pdf, properly paginated with headers/footers. Use this FOR archiving web pages as PDF, generating printable articles, saving receipts or invoices from URLs, or creating offline documentation snapshots. Do NOT use for custom documents from HTML/Markdown -- use document_generate_pdf instead. Do NOT use for screenshots -- use capture_screenshot instead. Do NOT use for web scraping text -- use web_scrape_to_markdown instead.
Output schemas not formally documented. Descriptions mention 'binary image' and 'binary PDF' but no structured schema (content-type, size, dimensions, metadata fields) is visible in code.
No error handling guidance. Descriptions do not explain what happens on invalid URLs, network timeouts, or rendering failures, or how the LLM should recover.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Both tools are read-only and idempotent but this is not formally declared in the schema.
Parameter descriptions lack format/constraint details. 'url' param says 'URL to screenshot' but does not specify protocol (http/https only?), max length, or validation rules.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 67 | 2025-06-18+ | v2 |
No pagination or batch variants. Tools accept single URLs only; agents calling repeatedly will waste tokens and latency.