Skip to main content
Glama
escapeWu

chrome-agent-bridge

by escapeWu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Watch Chrome tab events

browser_watch_events

Long-poll Chrome tab created, updated, removed, and activated events after a cursor.

Instructions

Long-poll tab created, updated, removed, and activated events after a cursor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabIdNoReturn only events for this tab.
browserNoWhich connected Chrome to use: an instanceId or label from browser_list_instances. Required when more than one browser is connected; session-based tools infer it from their sessionId.
timeoutMsNo
afterSequenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.1
    • addedInput schema / properties / browser
      Added value: +{
+  "description": "Which connected Chrome to use: an instanceId or label from browser_list_instances. Required when more than one browser is connected; session-based tools infer it from their sessionId.",
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv0.6.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses long-polling behavior, the event types, and cursor-based sequencing, which is useful. However, it omits timeout behavior, return shape, authentication requirements, and what happens when no events occur, leaving significant behavioral gaps for a no-annotation tool.

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?

The description is a single front-loaded sentence with no wasted words. It efficiently communicates the polling mechanism, event types, and cursor semantics in one compact statement.

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?

Given no annotations, no output schema, and only 50% schema description coverage, the description should carry more context. It does not explain timeout behavior, return format, or when to prefer this tool over related event or polling tools, making it insufficiently complete for the tool's complexity.

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?

Schema description coverage is 50%: tabId and browser are documented in the schema, but timeoutMs and afterSequence are not. The description partially compensates by implying the afterSequence param through 'after a cursor', but it adds nothing about timeoutMs and does not elaborate on filtering or browser selection.

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 names a specific action (long-poll) and resource (tab events), enumerating created, updated, removed, and activated events after a cursor. It clearly distinguishes this tool from generic event watchers by restricting to tab lifecycle events, though it does not explicitly contrast with siblings like browser_cdp_events.

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 states what the tool does but provides no guidance on when to use it versus alternatives such as browser_cdp_events or browser_network_poll. There are no preconditions, exclusions, or alternative-selection hints.

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

Deploy Server

Other Tools