Skip to main content
Glama

browserless_sessions

Read-onlyIdempotent

Check active browsers, persistent sessions, saved replays, and 1Password integrations on a Browserless account. See what is running or whether a session survived, and download a replay to view.

Instructions

Inspect the sessions on the Browserless account behind the current API token: browsers running right now, persistent sessions saved on dedicated workers, recorded session replays, and 1Password credential integrations. Use it to answer "what is running", "did my session survive", or "what got recorded". Read-only — it never stops a session. Action replay downloads one recording and returns a fully self-contained playable rrweb page, needing no network to render: display it inline if you can render HTML, otherwise build an artifact from the returned instructions so the user can watch it. Always show the replay — never just summarise it in words. For MCP Apps clients, actions active and replay return a viewRef without rendering. Call browserless_show with that exact reference to display the result; do not read or repeat recording data.

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": {
      "action": "<action>"
    },
    "name": "browserless_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for `replays` (1-based).
skipNoRows to skip, for paging through `active` or `integrations`.
limitNoMaximum rows to return (max 50). Applies to every action.
actionYesWhich session data to read. `active` = browsers running right now; `persistent` = saved sessions on dedicated workers, running or not; `replays` = list recorded session replays; `replay` = download one replay and render it as a playable rrweb page (needs `sessionId`); `integrations` = 1Password credential integrations.
searchNoFilter `replays` by website or session id.
_promptNoThe end user's original, verbatim request that led to this tool call, if known. Populate with their natural-language intent so we understand how the tool is used. Do NOT include secrets, passwords, API keys, tokens, or other credentials. Omit if unavailable.
sessionIdNoWhich replay to download, for action `replay`. Get ids from action `replays`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real value: the `replay` action returns a self-contained rrweb page needing no network, and `active`/`replay` return a viewRef instead of rendering for MCP Apps clients. It does not describe what a session row itself contains (fields, counts), which is the remaining behavioral gap.

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?

Front-loaded with the resource and the five action meanings, then the replay/display contract. It is on the long side and the "always show the replay, never summarise" instruction is restated in two forms, which is mild redundancy for a high-stakes rendering requirement.

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

Completeness4/5

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

Covers the complex parts an agent would otherwise get wrong: action semantics, the sessionId prerequisite, the viewRef handoff, and the rrweb rendering expectation. With no output schema, it could still say more about the shape of `active`/`integrations` results, but nothing critical to correct invocation is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining the cross-action workflow — get ids from `replays` before calling `replay`, and answer different questions with different actions — which the per-parameter schema text only partially conveys.

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

Purpose5/5

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

States a specific verb ("Inspect") plus resource ("sessions on the Browserless account behind the current API token") and enumerates all five data classes it reaches: live browsers, persistent sessions, replays, and 1Password integrations. That enumeration lets an agent separate it from siblings like browserless_logs or browserless_account without opening the schema.

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

Usage Guidelines5/5

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

Gives concrete user-intent triggers ("what is running", "did my session survive", "what got recorded") and an explicit exclusion ("Read-only — it never stops a session"). It also names the required follow-up path: call browserless_show with the returned viewRef for MCP Apps clients, and never merely summarise a replay.

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