Skip to main content
Glama
Browser MCP Server

Browser MCP Server

by xiaoguangpan

close_tab

Close a specified browser tab by tabId to remove it from the active Chrome or Edge session.

Instructions

Close a browser tab by tabId

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
tabIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 behavioral burden. It says nothing about whether the close is immediate or graceful, what happens to the active tab or the last remaining tab, whether the operation is reversible, or what errors occur for an invalid or already-closed tabId.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short phrase with the essential action front-loaded and no filler, which satisfies conciseness. However, the terseness reflects under-specification rather than disciplined economy.

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

Completeness2/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 param, no output schema, no annotations), which lowers the bar, but an agent still lacks the two things needed to call it reliably: where tabId comes from and what the post-close browser state looks like. For a destructive operation on browser state, that is a meaningful gap.

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 0% and the single parameter is typed only as 'number'. The phrase 'by tabId' merely restates the parameter name and adds no meaning about how to obtain a tabId, whether it must be currently open, or whether it can reference a background tab.

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?

The description states a specific verb and resource — 'Close a browser tab' — and the name plus the tabId reference make the operation unambiguous against siblings like open_tab and switch_tab. It stops short of explicitly naming a sibling it differs from, but the purpose is instantly recognizable.

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 a tab versus switching to it or opening a new one, and no mention of prerequisites such as needing a valid tabId obtained from the tabs tool. The only implied usage is the tautological 'close a tab when you want it closed.'

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