Skip to main content
Glama
frsorrentino

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

tab_action

Destructive

Manage browser tab lifecycle actions including close, activate, reload, back, forward, discard, mute, duplicate, or close session tabs. Provides precise control over tabs via Chrome Bridge.

Instructions

Tab lifecycle: close, activate, reload, back, forward, discard, mute, duplicate, close_session (only tabs this session created). close drops unsaved work and cannot be undone — it may be the user's tab. reload drops injected CSS, emulations and hooks. duplicate works where create_tab is forbidden (chrome-untrusted://) and lands in the source window, app windows included. discard replaces the tab id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesclose cannot be undone; discard frees memory (reloads on focus); reload drops injected CSS and hooks
tab_idNoTarget tab; omitted = last tab navigated in this session, else the active one
bypass_cacheNoreload only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.16.1
    • changedInput schema / properties / action / description
      Previous value: -"close cannot be undone; discard frees memory, the tab reloads on focus; reload drops injected CSS and hooks"New value: +"close cannot be undone; discard frees memory (reloads on focus); reload drops injected CSS and hooks"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "close",
-  "activate",
-  "reload",
-  "back",
-  "forward",
-  "discard",
-  "mute",
-  "unmute",
-  "duplicate"
-]New value: +[
+  "close",
+  "activate",
+  "reload",
+  "back",
+  "forward",
+  "discard",
+  "mute",
+  "unmute",
+  "duplicate",
+  "close_session"
+]
  2. Changed2 schema fields changedv1.15.0
    • changedInput schema / properties / action / description
      Previous value: -"close cannot be undone; reload drops injected CSS and page hooks"New value: +"close cannot be undone; discard frees memory, the tab reloads on focus; reload drops injected CSS and hooks"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "close",
-  "activate",
-  "reload",
-  "back",
-  "forward"
-]New value: +[
+  "close",
+  "activate",
+  "reload",
+  "back",
+  "forward",
+  "discard",
+  "mute",
+  "unmute",
+  "duplicate"
+]
  3. Changed2 schema fields changedv1.10.0
    • addedInput schema / properties / action / description
      Added value: +"close cannot be undone; reload drops injected CSS and page hooks"
    • addedInput schema / properties / tab_id / description
      Added value: +"Target tab; omitted = last tab navigated in this session, else the active one"
  4. First observedv1.8.0

TDQS

A4.4/5.0
Behavior5/5

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

The description discloses significant side effects beyond the annotations, such as close dropping unsaved work, reload dropping injections, and discard replacing the tab id. This goes well beyond the destructiveHint and idempotentHint flags, giving the agent clear expectations of consequences.

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 compact and information-dense, listing actions and consequences in a single readable paragraph. Every sentence contributes to understanding the tool's behavior and constraints, with no redundant or extraneous content.

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?

The description covers the main actions, side effects, and parameter semantics. It does not mention return values or error cases, but given the absence of an output schema and the operational nature of the tool, the context is adequately complete for most usage scenarios.

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?

The schema already provides descriptions for all parameters, including the enum meanings and the omission rule for tab_id. The tool description adds little extra semantic value beyond what is in the schema, so it meets the baseline for parameter coverage.

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?

The description clearly identifies the tool as performing tab lifecycle actions, listing all supported operations explicitly. It distinguishes from similar tools by noting that duplicate works where create_tab is forbidden, helping disambiguate from sibling tools like create_tab or move_tab.

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

Usage Guidelines4/5

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

It gives specific guidance on when to use certain actions, such as duplicate being available in restricted contexts and close_session applying only to tabs created in this session. It does not explicitly compare all actions to sibling tools, but the provided constraints are useful for agent decision-making.

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