Skip to main content
Glama

browser_close_tab

browser_close_tab
Destructive

Close a Chrome tab by its tab ID and owning session, preventing another session from closing a tab it does not hold.

Instructions

Close a Chrome 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": "browser_close_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYesChrome tab ID.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that — notably it is silent on what happens when the tab_id belongs to another session or does not exist, which the schema hints is a real failure mode.

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?

One sentence with zero waste, but also no front-loaded qualifiers or constraints to structure. It is concise without being padded; the brevity is the issue rather than verbosity.

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?

For a destructive 3-parameter tool, the description leaves out critical operational context: whether closing is immediate, what error surfaces for a session mismatch, and whether the tab group entry is removed. The annotations and rich schema cover some ground, but the description does not fill the remaining 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 description coverage is 100%, so tab_id, session_id, and session_name are fully documented in the schema, including the runtime refusal for another session's tab and the sticky grouping behavior. The description adds no parameter meaning, so baseline 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?

The description states a specific verb and resource ("Close a Chrome tab"), which is unambiguous about the action. It does not distinguish this from sibling operations like browser_claim_tab, browser_list_tabs, or browser_reset_sessions, so an agent must rely on name inference to know this is the per-tab close rather than a bulk/session-level close.

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 preconditions (e.g., the tab must be claimed by the current session), and no mention of alternatives for closing multiple tabs or resetting sessions. The agent gets only the imperative "Close a Chrome tab" with nothing to compare against.

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