Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

close_tab

Close a specified Google Chrome tab by its tab ID to remove unneeded pages and free browser resources.

Instructions

Close a tab in Google Chrome

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": "close_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYesTab ID to close

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description bears the full disclosure burden and supplies almost none. It does not say that closing discards the tab's page state and unsaved form input, whether the last/active tab can be closed, or what happens on an invalid tabId — all material for an irreversible operation.

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?

One short sentence, front-loaded with the verb and resource, with zero filler. Nothing in it is redundant or padded.

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?

The tool is simple (one required string param, no output schema, no nested objects), so a one-liner is defensible. However, the absence of annotations leaves the destructive nature and failure conditions entirely unexplained, which is a real gap for a close operation.

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 single tabId parameter is fully documented in the schema ("Tab ID to close"), so schema coverage is 100% and the baseline is 3. The description adds no meaning beyond that — no format hint, no note that IDs come from list_tabs.

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?

"Close a tab in Google Chrome" states a specific verb (close) and resource (tab), which is clearly distinguishable from siblings such as new_tab, switch_to_tab, and reload_tab. It stops short of naming any sibling or scoping which tab, but the core action is unambiguous.

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 when-to-use guidance, no precondition (e.g. the tab must exist and be open), and no pointer to list_tabs or get_current_tab as the way to obtain a valid tabId. The agent must infer all of this from sibling names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.