Skip to main content
Glama
chrome-remote-debugging-mcp

chrome-remote-debugging-mcp

by danilin-em

close_tab

Close a Chrome tab opened earlier by browse or navigate, dropping its refs and returning closed status or error.

Instructions

Close a Chrome tab opened earlier (e.g. by browse / navigate).

Its refs are dropped along with it. Returns {"tab_id", "closed": True} or {"error": ...}.

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

Input Schema

NameRequiredDescriptionDefault
tab_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose a real side effect ('its refs are dropped along with it') plus the return shape on success and the error shape. It stops short of stating whether the call is idempotent, whether closing affects other tabs or sessions, or what an error means in practice.

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?

Three short sentences, front-loaded with the action, followed by the side effect and the return contract. Nothing is padded or restated from the schema.

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, non-destructive-in-spirit tab-management tool with no output schema, the description covers purpose, key side effect, and return values adequately. The only meaningful omission is the failure/staleness semantics and how a tab_id is sourced when it wasn't just created by browse/navigate.

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 0% for the single required parameter, so the description must compensate; it does so partially by indicating the tab_id refers to a tab opened earlier by browse/navigate. It never states the id format or how to obtain a tab_id for a tab the agent did not just open, leaving part of the parameter semantics unresolved.

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?

States a specific verb and resource ('Close a Chrome tab') and anchors it to the sibling tools that create tabs ('e.g. by browse / navigate'), so an agent can tell it apart from navigate/browse_view without ambiguity. It does not explicitly contrast with list_tabs or other tab-management siblings, keeping it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'opened earlier (e.g. by browse / navigate)' implies the precondition that the tab must already exist and roughly where it came from, which is useful contextual guidance. However, there is no explicit when-not-to-use, no statement about what happens with an invalid or already-closed tab_id, and no pointer to list_tabs for discovering an existing tab's id.

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