Skip to main content
Glama
escapeWu

chrome-agent-bridge

by escapeWu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Activate Chrome tab

browser_activate_tab

Activate a selected Chrome tab and focus its window so agents can continue interacting with the correct page; specify tabId, and browser when multiple instances are connected.

Instructions

Activate a Chrome tab and focus its window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabIdYes
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.

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

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It hints at a focus-changing side effect, but says nothing about what happens if tabId is stale/nonexistent, whether the call is idempotent, whether it requires the browser to be attached, or whether activating steals OS-level focus. One clause is not enough for a mutation-style browser action.

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?

A single front-loaded sentence with no filler or repeated schema content. It is appropriately terse, though arguably so terse that required context is omitted rather than merely compressed.

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 browser-mutating tool with no annotations, no output schema, and an undocumented required parameter, this definition is incomplete. It omits the connected-browser prerequisite, the origin of tabId, and the failure behavior, leaving meaningful gaps for an agent to guess at.

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 coverage is 50%: the browser parameter is documented in the schema (instanceId/label from browser_list_instances), but tabId — the required parameter — has no description anywhere. The description does not explain where a tabId comes from (browser_list_tabs / browser_open_tab) or what values are valid.

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 (activate) and resource (Chrome tab) plus the side effect of focusing the window, which cleanly separates it from browser_open_tab, browser_close_tab, and browser_list_tabs. It does not name those siblings explicitly, 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?

No when-to-use guidance, no statement of the precondition that a browser must be connected, and no routing advice versus browser_open_tab (which also results in an active tab) or browser_navigate. The agent must infer the calling context entirely.

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