Create a stateful browser session that persists cookies and localStorage across multiple scrape/workflow calls.
| Name | Required | Description | Default |
|---|---|---|---|
| ttl_seconds | No | Session TTL (default 1800, max 7200) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses key behavioral trait: persistence of cookies and localStorage. Without annotations, this helps agents understand statefulness. Could mention session expiration behavior or resource limits, but adequate for the tool's simplicity.
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 that is efficient and front-loaded with the core purpose. No wasted 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?
Given low complexity (one optional parameter, no output schema), the description covers the essential behavior. Missing return value (likely a session ID), but implied for creation tools.
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?
Input schema covers 100% of parameters with descriptions. The tool description adds no additional explanation beyond schema. Baseline 3 is appropriate.
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?
Description clearly states the tool creates a stateful browser session that persists cookies and localStorage. It uses a specific verb ('Create') and resource ('browser session'), and distinguishes from stateless sibling tools like scrape_webpage.
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?
Implies usage for scenarios needing persistence across multiple calls, but lacks explicit when-not-to-use or alternative recommendations. However, the context of sibling tools provides implicit guidance.
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.