Skip to main content
Glama

browser_open

browser_open

Opens a URL in Chrome or navigates an existing tab when a tab ID is supplied, enabling agents to control the signed-in browser.

Instructions

Open a URL in Chrome, or navigate an existing tab when tab_id is given.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
tab_idNo
activateNo
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare not-read-only, openWorld, non-idempotent and non-destructive, so the safety profile is covered. The description adds the open-vs-navigate distinction but says nothing beyond annotations about the resulting tab: whether it becomes focused, whether it waits for load, or what happens when the URL fails. Reasonable but thin.

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?

One front-loaded sentence with two clauses that each carry meaning. No padding, no redundancy.

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

Completeness2/5

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

For a 5-parameter browser navigation tool with no output schema, the definition leaves key behavior unexplained: what a new tab does (focus, load waiting) and what activate means, which nothing else in the structured data covers. It is adequate only for the two-parameter happy path.

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

Parameters2/5

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

Only url and tab_id are covered by the description. activate is undocumented in both the description and the schema, session_id and session_name rely entirely on their inline schema text, and schema coverage is 40%. The description should explain the activate behavior, since that is the one parameter no structured field defines.

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 a URL in Chrome") plus the second mode ("navigate an existing tab when tab_id is given"). It cleanly separates the new-tab and existing-tab cases, though it does not name a sibling such as browser_switch_tab or browser_claim_tab to disambiguate.

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 gives one conditional: pass tab_id to navigate an existing tab, otherwise open new. That implies usage but omits any exclusion guidance, e.g. whether to prefer browser_switch_tab for focus-only changes or how session_id interacts with a tab that another session holds.

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