Skip to main content
Glama

create_browser_session

Start browser automation by creating a new session with intelligent auto-close and workflow-aware management.

Instructions

Create a new browser session with intelligent auto-close and session management

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
browser_typeNoBrowser engine to use. Chromium offers best compatibility and stealth features, Firefox for privacy, Webkit for Safari-like behavior
headlessNoBrowser runs in headless mode (no UI) for optimal performance and stealth. Always defaults to true for AI automation
javascript_enabledNoWhether to enable JavaScript execution for proper page rendering. Recommended to keep enabled for modern websites
viewport_widthNoBrowser viewport width in pixels. Affects how pages are rendered and responsive design
viewport_heightNoBrowser viewport height in pixels. Affects how pages are rendered and responsive design
user_agentNoCustom user agent string. If not provided, a realistic Chrome user agent will be generated automatically for better stealth
agent_idNoAgent identifier for tracking which AI agent created this session. Used for memory and knowledge graph integration
auto_closeNoWhether to automatically close the session after inactivity. Documentation sessions ignore this setting to prevent data loss
workflow_typeNoType of workflow this session will be used for. Documentation sessions have special handling to prevent auto-close, automation sessions optimize for speed, testing sessions focus on reliabilityautomation
session_timeoutNoMaximum session lifetime in milliseconds before auto-close (default: 30 minutes)
max_idle_timeNoMaximum idle time in milliseconds before session is considered stale (default: 10 minutes)
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses auto-close behavior, workflow-specific handling, timeout/idle settings, and stealth features (e.g., auto-generated user agent). It does not cover failure states or rate limits, but the behavioral context is strong.

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?

The description is a single, front-loaded sentence that succinctly captures the tool's purpose. No redundant information; every word serves a clear function.

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?

Given the complex input schema (11 parameters with good descriptions) and no output schema, the description provides sufficient high-level context. It covers essential behavioral aspects like auto-close and workflow awareness, though it omits mention of return value (e.g., session ID).

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 description coverage is 100%, with detailed descriptions for all 11 parameters. The description adds high-level context (e.g., 'intelligent auto-close') but does not significantly enhance individual parameter semantics beyond what the schema already provides.

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?

The description states 'Create a new browser session with intelligent auto-close and session management', which clearly indicates the verb and resource. It distinguishes from sibling tools like 'close_browser_session' and 'list_browser_sessions' by emphasizing creation and management features.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description hints at usage contexts through the workflow_type parameter (documentation, automation, testing) and mentions special handling for documentation sessions. However, it does not explicitly state when to use this tool over alternatives or provide exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ZachHandley/ZMCPTools'

If you have feedback or need assistance with the MCP directory API, please join our Discord server