Skip to main content
Glama
escapeWu

chrome-agent-bridge

by escapeWu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Close bridge-created Chrome tab

browser_close_tab

Close a Chrome tab created by Chrome Agent Bridge in the current extension session to clean up agent-opened tabs.

Instructions

Close a tab only when it was created by Chrome Agent Bridge in the current extension session.

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

B3.4/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 and does disclose one meaningful behavioral constraint (session-scoped, bridge-created tabs only). However it omits what happens on a violation (error vs. no-op), whether the close is irreversible, and any permission requirements, leaving notable gaps for a destructive operation.

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 the verb first and the guard condition second; nothing is wasted. It is terse to the point of omitting necessary behavioral detail, but as structure it is clean.

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

Completeness3/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% parameter coverage, the definition is only minimally complete. It establishes scope but leaves failure modes, return behavior, and the tabId parameter unaddressed, so an agent can select it but not confidently invoke it in edge cases.

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 only 50%: browser is documented in the schema but tabId has no description anywhere, and the description adds no parameter meaning at all. The tool's central identifier (tabId) is therefore unexplained in both places, which the description should have compensated for.

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 (Close) and resource (a tab) plus the eligibility condition (bridge-created in the current extension session), which separates it from generic tab tools. It does not name a sibling alternative or otherwise contrast with browser_list_tabs/browser_activate_tab, so it falls 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 Guidelines4/5

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

Provides a clear precondition for use: only close tabs created by Chrome Agent Bridge in the current session, which implicitly tells the agent when NOT to use it. No explicit alternative is named for the case where the tab was user-created, so it is clear context without full when/when-not routing.

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