Skip to main content
Glama

Browse Bridge

by com.browsebridge
OverviewDiscussionsAdmin

Get session status

browser_get_status
Read-onlyIdempotent

Get control mode and tab status for a session. Includes the current url, offOrigin when that url is outside allowedOrigins, sensitiveMode, and deviceOnline. sensitiveMode is true when Sensitive site is on: click, type, key, and navigation wait for Approve (APPROVAL_REQUIRED), which is not CHALLENGE_DETECTED. When the device heartbeat is stale, controlMode is disconnected and statusUx is SESSION_OFFLINE, not HUMAN_HAS_CONTROL. Includes remaining monthly quota (actionsRemaining, screenshotsRemaining), quotaExceeded, and quotaResetAt (ISO). dialogHook is { installed, error?, rawError? }. error and rawError are the Chrome scripting error, not a rewritten content-script message. statusUx and blocked keep a stable code; rawError is the Chrome string when it differs from the friendly message. statusUx names CHALLENGE_DETECTED, ORIGIN_NOT_ALLOWED, SESSION_OFFLINE, or HUMAN_HAS_CONTROL when the human must take over. CONTENT_SCRIPT_UNAVAILABLE is returned from tools if the agent is not on the tab. EXTENSION_RECONNECT_NEEDED means click Reconnect in the side panel, then retry. While a JavaScript dialog is open, dialog is { type, message, pending: true } and blocked.code stays JS_DIALOG_OPEN. A native HTTP sign-in prompt is HTTP_AUTH_REQUIRED in blocked and statusUx, with dialog null. The user answers or cancels it. Browse Bridge does not enter the username or password. Navigate, back, forward, and reload can leave that prompt. A timeout while that dialog is open is DIALOG_PENDING, not CONTENT_SCRIPT_UNAVAILABLE. In Agent mode, alert/confirm/prompt stay pending until browser_handle_dialog. They are not dismissed when they open. QUOTA_EXCEEDED names which quota (actions or screenshots) and resetAt. extensionVersion is the connected extension, sent on the WebSocket handshake and the first auth frame. meetsExtensionMinimum and meetsLatestExtension compare it with extensionMinVersion and latestExtensionVersion.

Input Schema

NameRequiredDescriptionDefault
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior5/5

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

The description adds extensive behavioral context beyond the annotations: sensitive-mode approval behavior, stale heartbeat handling, quota tracking, dialog states, Chrome error distinction, and extension version compatibility checks. This is far more than the readOnly/idempotent annotations provide.

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 appropriately front-loaded, but the rest is a dense, long block of status-code details. Much of it is relevant, yet the structure is hard to scan and could be organized more clearly.

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?

Because there is no output schema, the description carries the burden of explaining return values, and it does so extensively with status codes, quota fields, dialog shapes, and error semantics. It is only missing sessionId sourcing and usage guidance.

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% for the single required sessionId parameter. The description only says 'for a session' and does not explain where to obtain sessionId, its expected format, or how it relates to browser_list_sessions.

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 first sentence states a specific verb and resource: 'Get control mode and tab status for a session.' It is clearly a status-reading tool, though it does not explicitly distinguish itself from siblings like browser_observe or browser_list_sessions.

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?

The description explains many status codes and behaviors but never says when to call this tool versus alternatives such as browser_observe or browser_list_sessions. There is no explicit when-to-use or when-not-to-use guidance.

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

All Browse Bridge toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources