Skip to main content
Glama

List sessions

browser_list_sessions
Read-onlyIdempotent

List browser sessions the user has delegated. If this connector is signed into a different Browse Bridge account than the extension on the same browser, the result is ACCOUNT_MISMATCH instead of an empty list. A session with an open JavaScript dialog includes dialog: { type, message, pending: true }. A native browser sign-in prompt includes blocked.code HTTP_AUTH_REQUIRED and does not set dialog. title is the document title. A page with no title, and Chrome's URL fallback (including host/path with no scheme), is an empty string.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

The description goes well beyond the annotations, which only declare readOnly/idempotent/non-destructive. It discloses a distinct failure mode (ACCOUNT_MISMATCH rather than an empty list), a dialog representation with pending flag, an auth-blocked signal via blocked.code HTTP_AUTH_REQUIRED, and the title fallback behavior are all non-obvious behaviors an agent could not get from the structured fields.

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

Conciseness3/5

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

The first sentence is well front-loaded, but the remainder reads as a stitched sequence of edge-case gotchas rather than an organized account of the return shape. Sentences like 'A native browser sign-in prompt includes blocked.code HTTP_AUTH_REQUIRED and does not set dialog' pack real information but are terse and unglossed.

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 no output schema, the description carries the full burden of describing the return value, and it covers only a subset: error paths, dialog, and title. It never states what a session entry fundamentally contains (identifier, url, open tabs), which is what an agent most needs from a list 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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The text correctly avoids inventing parameter discussion and spends its budget on result semantics instead.

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 opening sentence gives a specific verb+resource: 'List browser sessions the user has delegated.' That is enough to distinguish it from the action-oriented siblings (click, navigate, observe), none of which are enumerations. It stops short of explicitly contrasting with browser_get_status or browser_observe, which could plausibly be confused with it.

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?

Usage is implied by the listing verb and the scoping phrase 'the user has delegated', so an agent can infer it is the discovery entry point. But there is no explicit when-to-use, no statement of what to do after a listing, and no routing to alternatives such as browser_get_status.

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.