Skip to main content
Glama
Sign In
MCP Browser

MCP Browser

by wgarrido
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

close_tab

Close a browser tab by its tab ID to clean up after browsing sessions and avoid clutter from tabs opened during automation.

Instructions

Close a persistent browser tab by its tab_id. Use this to clean up tabs opened with open_tab.

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": {
      "tab_id": "<tab_id>"
    },
    "name": "close_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYesThe tab ID returned by open_tab

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It clearly discloses that the operation closes a tab and is intended for cleanup, which implies a mutating action. However, it does not mention side effects, error behavior, or whether the close is irreversible.

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?

Two concise sentences, with the core action front-loaded and the usage context in the second sentence. No filler or redundant wording.

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?

For a single-parameter tool with no output schema, the description is largely complete: it states what is closed, what identifier is needed, and when to use it. It could mention return/error behavior, but the simplicity of the operation makes this a minor gap.

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 coverage is 100%, with tab_id already documented as 'The tab ID returned by open_tab'. The description restates this relationship but adds no significant new semantic detail beyond what the schema provides.

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 uses a specific verb ('Close') and resource ('persistent browser tab') and identifies the exact identifier needed ('by its tab_id'). This is clearly distinguishable from siblings like open_tab and list_tabs.

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?

The description explicitly states when to use the tool: 'Use this to clean up tabs opened with open_tab.' It does not provide when-not-to-use guidance, but there is no alternative close tool among the siblings, so this is sufficient.

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