Skip to main content
Glama

Open a browser

open_browser

Open one remote browser in the cloud with the connected CloudBrowser account. Use it only for websites and accounts that the user owns or is authorized to use, and follow their terms. Browsers open without stealth fingerprints.

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": "open_browser"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoSpecifies the instance name, useful for recognizing it in the list of open remote desktops
browserNoBrowser type: 0 = Chrome, 2 = Chromium, 3 = ChromeHeadlessShell. Default 0
headlessNoIndicates whether the browser should open in headless mode (true) or with GUI (false). Default false
keepOpenNoSeconds of inactivity before browser closes automatically. Value 0 is never, default 300 seconds
saveSessionNoIf true, browser session is saved periodically and at the end, cookies and local storage, but not open tabs. Default false
recoverSessionNoIf true, loads the label when starting a previous session (if it exists), to know which session we save/restore. Default false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / args
      Removed value: -{
      -  "description": "List of custom browser arguments. If null, default arguments will be used",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / ignoredDefaultArgs
      Removed value: -{
      -  "description": "List of default arguments to ignore. If null, default ignored arguments will be used",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / stealth
      Removed value: -{
      -  "default": true,
      -  "description": "Enable or disable stealth mode. Default true",
      -  "type": "boolean"
      -}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the mutation/safety profile is largely covered. The description adds one genuinely new behavioral fact — 'Browsers open without stealth fingerprints' — plus the authorization expectation. It omits other useful context: whether opening consumes a limited account slot, what happens if a browser is already open, and what identifier is returned. Note that browsing arbitrary websites sits oddly with openWorldHint=false, though the tool itself only provisions the browser, so this is not a clear contradiction.

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?

Three short sentences, front-loaded with the core action, then the constraint, then a behavioral note. Nothing is redundant or padded. It is not maximally tight — the authorization sentence is somewhat boilerplate — but structure is sound.

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?

With full schema coverage and annotations covering the safety profile, the definition is close to sufficient for a zero-required-parameter provisioning tool. The remaining gap is the outcome: there is no output schema and the description never indicates what the caller receives (browser id, label, connection handle) or how it relates to connect_to_browser. Adequate but with a visible hole.

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 all six parameters, including defaults and the browser enum mapping, fully documented in the schema. The description adds no parameter meaning beyond that, which is acceptable at this coverage level but earns only the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Open one remote browser in the cloud with the connected CloudBrowser account.' That clearly separates it from close_browser, get_browsers, and connect_to_browser. It does not explicitly distinguish itself from plausible siblings like browser_workspace or start_remote_desktop, so it stops short of a 5.

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

Usage Guidelines3/5

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

The description supplies a policy-level constraint ('only for websites and accounts that the user owns or is authorized to use, and follow their terms'), which is real guidance but of a compliance kind. It never says when to choose this over alternatives such as start_remote_desktop, browser_workspace, or resume_saved_session, so the routing decision is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources