Skip to main content
Glama
Sign In
BrowserMCP Extended

BrowserMCP Extended

by NEO10111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_close_tab

Close a browser tab by its numeric tab ID to remove unwanted tabs and free browser resources.

Instructions

Close a browser tab by its tab ID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tabId": "<tabId>"
    },
    "name": "browser_close_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYesNumeric ID of the tab to close

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose that this is an irreversible action (any unsaved page state is lost), whether it fails on the final tab, or whether the ID must be a live tab rather than a stale one.

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. Nothing is wasted, though there is also nothing extra to justify a top score.

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?

For a one-parameter tool with full schema coverage and no output schema, the definition is technically sufficient to invoke. However, with zero annotations it leaves the destructive nature and tab-ID provenance unexplained.

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 100% and the single parameter is already documented as 'Numeric ID of the tab to close'. The description's 'by its tab ID' adds no syntax or sourcing detail beyond the schema, so the baseline of 3 applies.

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 browser tab') with the identifying parameter. It is distinguishable from browser_new_tab / browser_switch_tab by the verb, though the description never names those siblings explicitly.

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?

There is no guidance on when to close versus switch away, no note that tabId typically comes from browser_list_tabs, and no mention of what happens when the last tab is closed. The agent must infer all of this.

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