Capture a PNG screenshot of any webpage. Supports desktop, mobile, and tablet viewports, plus full-page mode.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| wait_ms | No | ||
| viewport | No | ||
| wait_for | No | ||
| full_page | No | Capture full scrollable page (default: false) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations lack readOnlyHint, destructiveHint, etc. Description adds viewport and full-page support but omits details like permissions, error handling, or what happens on failure. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with purpose. Efficient and to the point without unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool is straightforward, but description lacks information about the output format (e.g., base64 PNG, file path) and no output schema. Adequate for basic usage but incomplete for full agent understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only 20% of parameters have schema descriptions. Description adds meaning for viewport and full_page but fails to explain wait_ms and wait_for, which are crucial for timing. Schema coverage is low, and description does not fully compensate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it captures a PNG screenshot of any webpage, with support for viewports and full-page mode. It effectively distinguishes from sibling tools like scrape_webpage (text extraction) and extract_structured_data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description implies usage for screenshots with various viewports but provides no explicit guidance on when to use this tool vs alternatives, no prerequisites, 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.
Add one secure layer between your agents and this server.
Each tool serves a distinct purpose: session management, metadata extraction, AI-powered data extraction, multi-step workflows, content scraping, and screenshot capture. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with underscores (e.g., create_browser_session, extract_metadata, run_workflow), making it predictable and easy to understand.
With 6 tools, the server covers the essential operations for web scraping and automation: session management, content retrieval, metadata extraction, structured data extraction, screenshots, and complex workflows. The count is well-scoped and not excessive.
The tool set covers core scraping tasks comprehensively, including advanced workflow automation. Minor gaps exist, such as no explicit tool for direct cookie manipulation or DOM inspection, but the workflow tool can compensate. Overall, it is sufficiently complete for typical use cases.