Skip to main content
Glama

tab_close

Closes a specified browser tab by its ID from tab_list, so you can safely remove only tabs you opened or were asked to close.

Instructions

Close a tab in the user's browser by its id from tab_list. Close only tabs you opened or were asked to.

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
tabIdYesId of the tab to close, from tab_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden for a destructive, likely irreversible operation. It adds a useful ownership/safety rule beyond the schema, but never states that closing is irreversible, what happens to unsaved or in-progress page state, or how it behaves on an invalid id or the last remaining tab. That leaves a meaningful gap for a close operation with zero annotation coverage.

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 short sentences with the action stated first and the safety constraint second; every clause carries information and nothing is padded. The provenance pointer (tab_list) is embedded efficiently in the opening sentence.

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 one-parameter tool with no output schema and no annotations, the definition covers the essentials: what it does, where the id comes from, and a policy on which tabs are eligible. It would be complete at 5 if it noted irreversibility or the failure mode for an invalid or already-closed tab.

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 the single tabId parameter is already documented in structured data, and the description's "by its id from tab_list" only reinforces provenance. It adds no meaning about id ranges, validity, or what happens when the id is stale, so baseline 3 is appropriate.

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 names a specific verb and resource ("Close a tab") and states the scope ("in the user's browser"), which separates it from read-only siblings like tab_read or tab_list. It also points to tab_list as the source of the identifier, giving the agent a concrete way to obtain the required value. It stops short of explicitly naming what it is not (there is no sibling that also closes tabs), so it sits at a clear but not fully differentiated 4.

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?

"Close only tabs you opened or were asked to" is a genuine when-to-use constraint that tells the agent which tabs are in scope and which are off-limits, which is more than most mutation tools provide. It gives no explicit when-not condition beyond that ownership rule and names no alternative tool, so it is clear context without full exclusions.

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