Skip to main content
Glama

List open browser sessions

writ_browser_sessions
Read-onlyIdempotent

Lists the account's open cloud browser sessions (each resumable by its session_id).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
include_closedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_closed
      Added value: +{
      +  "type": "boolean"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / properties / include_closed
      Removed value: -{
      -  "description": "Also lists recently closed sessions (not resumable) for reference. Default false: only open, resumable sessions.",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / limit / description
      Removed value: -"Max sessions to return (default 20)."
  3. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds genuinely new context that each session is resumable via session_id, but it is silent on pagination/default limit behavior and on how include_closed interacts with the stated "open" scope.

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?

A single front-loaded sentence with no filler; the resource and its scope appear immediately and the parenthetical adds value rather than repeating the title.

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 simple read-only list tool the description could be complete, but with 0% schema coverage and no output schema, the agent is left guessing what limit and include_closed do and what shape the returned session list takes. The definition should state the default filtering and pagination semantics.

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?

Schema description coverage is 0%, so neither parameter is documented anywhere except its name. The description does not explain what limit does, whether it is a page size or a cap, what the default is, or that include_closed overrides the "open sessions" scope implied by the first sentence — a meaningful gap for a two-parameter tool.

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 ("Lists the account's open cloud browser sessions") and adds that each is resumable by its session_id, which tells the agent what the returned identifiers are for. It does not differentiate itself from siblings like writ_browser_use or writ_browser_context, 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 Guidelines2/5

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

There is no statement of when to call this versus alternatives (e.g., to discover an existing session before starting a new one with writ_browser_use), and no prerequisites or exclusions. Usage must be inferred from the phrase "lists open sessions" alone.

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.