Skip to main content
Glama

Open a browser session

browser_open

Open a browser session to handle logins, forms, and portals, then control it with other browser tools.

Instructions

Open a browser session you drive with the other browser_* tools. A cloud backend BILLS FOR EVERY MINUTE; local is free on this machine, and headless=false shows its window. For logins, forms and portals: ask the user first, and browser_close when done (idle 300s ends it; at most 3 open). Unset provider with stealth, proxy_country or solve_captchas routes to a BILLED vendor.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNoSeconds the session may live; unset, 600.
headlessNoWith `local`, false shows a window on this machine.
providerNo
viewportNoIn CSS pixels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.14.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations (readOnly=false, openWorld=true, idempotent=false, destructive=false) by disclosing cost behavior (cloud backend bills per minute, local is free), a 300s idle termination, and a cap of 3 concurrent sessions. It does not say what is returned (e.g. a session handle/ID) or how billing interacts with the timeout parameter, leaving a small gap.

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?

Front-loads the purpose, then cost, then lifecycle in a compact block with no filler. The telegraphic style and heavy caps/backticks make it dense to parse but do not waste words; slightly more connective phrasing would aid readability without adding length.

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

Completeness3/5

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

Covers cost, concurrency limits, idle expiry, and the user-consent requirement for a stateful, open-world tool, which is substantial. However, with no output schema present, the description never states what the call returns (session identifier or handle) that the other browser_* tools presumably need, which is a meaningful omission for a session-creating tool.

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

Parameters4/5

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

Schema coverage is 75%, so much is already documented, but the description adds real meaning the schema lacks: the consequence of leaving provider unset, and the interaction between headless=false and the local provider. timeout and viewport are left entirely to the schema.

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?

States a concrete verb+resource (open a browser session) and immediately ties it to the browser_* family of sibling tools that drive it, so it is distinguishable from browser_close, browser_goto, etc. without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use context (logins, forms, portals), a required precondition (ask the user first), and a lifecycle rule (call browser_close when done). It also spells out the routing condition that selects a billed vendor (unset provider combined with stealth, proxy_country, or solve_captchas), which is exactly the decision point an agent needs.

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