Skip to main content
Glama

browser_new_session

Create a new browser session with stealth features for automated tasks, including proxy, persistence, headless, humanization, and recording options.

Instructions

Create a new stealth browser session and make it current. Returns its id.

    Runs PROXYLESS by default. To use a proxy, pass either proxy_url
    ('http://user:pass@host:port') or proxy_server[+username/password].
    no_proxy=True forces proxyless even if an env/default proxy is configured.

    persistent: keep cookies/localStorage in a profile dir across runs.
    headless: override the configured default (None = use the default).
    humanize: per-session cursor humanization — a float caps cursor-move time in seconds
        (e.g. 0.25 = fast but still humanized), True = default speed, False = off,
        None = use the configured default.
    record_har: capture a full network HAR (export with browser_har_export).
    record_video: record the session to a native .webm (Chromium only); fetch the path with
        browser_video_path. The file is finalized on browser_close_session.
    record_video_width / record_video_height: pin the recording resolution (e.g. 1920 x 1080
        for HD); when omitted Playwright defaults to 800x450.
    har_url_filter: glob to scope what the HAR records (e.g. '**/api/**' or
        '**/students/**') so it excludes login/captcha/static noise; default = all.
    storage_state: path to a saved cookies/localStorage JSON to reload.
    extensions: list of paths to UNPACKED Chromium extension folders to side-load (e.g. a
        captcha-solver or a custom extension). Forces a persistent + headful session
        (Chromium only side-loads extensions that way); the profile persists so the
        extension's own config/login survives.
    Most tools auto-create a default session, so calling this is optional.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
persistentNo
labelNo
headlessNo
humanizeNo
record_harNo
record_videoNo
record_video_widthNo
record_video_heightNo
har_url_filterNo
storage_stateNo
extensionsNo
proxy_urlNo
proxy_serverNo
proxy_usernameNo
proxy_passwordNo
no_proxyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, so the description carries full transparency burden. It covers key behaviors: proxyless by default, proxy options, persistence, headless mode, humanization, recording HAR/video, storage_state reload, and extensions forcing persistent+headful. It also states that most tools auto-create a default session. The only gaps are missing details on rate limits or authentication, which are not critical for this tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and return value. Parameter explanations are grouped in a bullet-like structure (plain text but logically formatted). While a bit lengthy (several lines), each sentence provides necessary detail; no redundancy. It strikes a good balance between completeness and readability, though could be slightly more compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high complexity (16 parameters, zero schema descriptions, no annotations), the description is exceptionally complete. It covers every parameter's behavior, side effects (extensions force persistent+headful), optionality, and return value. The only minor omission is the exact format of the returned id, but since it's a simple string, this is acceptable.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must fully explain parameters. It does so thoroughly: for each parameter it explains purpose, defaults, constraints (e.g., extensions forces persistent+headful), and acceptable values (e.g., humanize: float, bool, or None). This adds immense value beyond the bare schema, making the agent capable of correct parameter choices.

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 opens with 'Create a new stealth browser session and make it current. Returns its id.' This clearly states the verb (create), resource (stealth browser session), and outcome (makes current, returns id). It distinguishes this tool from siblings like browser_close_session or browser_list_sessions, as it is the only session creation tool.

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 explicitly notes that 'Most tools auto-create a default session, so calling this is optional.' This tells the agent when the tool is needed (custom settings) and when it's not (default behavior). It also explains proxyless default and how to override, providing clear context for usage. However, it does not explicitly list alternatives or when-not scenarios beyond the optionality statement.

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/Evil-Bane/eyebrowse'

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