Skip to main content
Glama

browser_windows

Lists open browser windows with their focus state and automation session names, helping you identify the correct window to target for browser automation.

Instructions

List browser windows, focus state and automation session names in each window.

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_windows"
  }
}

Input Schema

NameRequiredDescriptionDefault
browserNoBrowser id from browser_list, or chrome/firefox when only one instance matches.

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?

No annotations are supplied, so the description carries the full burden. It does disclose the return content (windows, focus state, session names), which is useful since there is no output schema, but it omits behavior on edge cases such as no open browsers, no active automation session, or whether the call is strictly read-only.

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?

One tight sentence with the main purpose front-loaded and no filler. The triple-list construction of return fields is slightly dense but still readable in a single pass.

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?

For a zero-required-parameter listing tool with no output schema and no annotations, the description covers the essentials of what is returned. It falls short on behavioral edges (empty results, session absence) and on how it relates to browser_list, which an agent would likely need.

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?

The single browser parameter is fully described in the schema, including the fallback to chrome/firefox when only one instance matches, so the schema does the heavy lifting. The description adds nothing about the parameter, which is acceptable at 100% coverage but is not additive.

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?

The description gives a specific verb and resource ("List browser windows") and enumerates the payload (focus state, automation session names per window), so the agent knows exactly what it gets back. It does not explicitly distinguish itself from the similarly named browser_list, which also appears in the sibling set, leaving the browser-vs-window distinction to be inferred.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no pointer to an alternative such as browser_list or browser_focus. The agent must infer from the name alone that this is the discovery step before window-scoped operations.

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