Skip to main content
Glama

tab_close

Closes a specified browser tab by ID, or the last agent tab when no ID is supplied, to keep browser sessions organized and reduce open-tab clutter.

Instructions

Close a 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": {
      "tabId": "<tabId>"
    },
    "name": "tab_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYesAgent tab id from tabs_list. Omit to use the last agent tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.4

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses almost nothing: not whether closing is reversible, what happens to the page state, whether the last remaining tab can be closed, or what is returned. Only the bare mutating nature of "close" is communicated.

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?

The single sentence is free of waste but is under-specified rather than concise; there is no front-loaded context beyond the obvious action. Nothing needs trimming, but nothing earns much credit either.

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 state-mutating browser action with no annotations and no output schema, the description leaves key questions unanswered: what the agent observes after closing, what happens if tabId is invalid, and any restrictions on which tab can be closed.

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%, and the schema itself documents tabId including the fallback to the last agent tab, so the description adds no parameter meaning. Baseline 3 applies since the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Close a tab" states a verb and resource, but it essentially restates the tool name tab_close with no additional specificity. It does not clarify scope relative to siblings such as tab_open or tabs_list.

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?

No when-to-use or when-not-to-use guidance is provided. Nothing tells the agent how this relates to tab_open or whether closing is expected as part of a workflow; the only hint is a parameter description in the schema.

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