Skip to main content
Glama
Sign In
Browser Control

Browser Control

by PrinceGarth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

close-browser-tabs

Close browser tabs by ID to remove unwanted pages while leaving other tabs open, useful for managing Browser Control sessions.

Instructions

Close tabs in the user's browser by tab IDs

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": {
      "tabIds": "<tabIds>"
    },
    "name": "close-browser-tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdsYes

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?

No annotations are provided, so the description carries the full behavioral burden. It does not disclose that closing tabs is irreversible, whether it requires specific permissions, or what happens with invalid IDs; it merely restates the mutation.

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?

The description is a single, front-loaded sentence with no wasted words. Its brevity is appropriate for conciseness, though it borders on under-specification for a destructive operation.

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?

With no annotations, no output schema, and a required parameter at 0% schema coverage, the description is too thin. It should clarify irreversibility, ID sourcing, and error behavior to be complete for safe invocation.

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?

The schema has 0% description coverage, so the description must compensate. It mentions 'by tab IDs', which adds meaning to the tabIds parameter, but it does not explain the array nature, number type, or where to obtain the IDs.

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 (close) and resource (browser tabs), and specifies the mechanism (by tab IDs). It does not explicitly differentiate itself from siblings like get-list-of-open-tabs or open-browser-tab, but the action is unambiguous.

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 use this tool versus alternatives, nor any prerequisites such as needing tab IDs from get-list-of-open-tabs. Usage is only implied by the verb 'close'.

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

Deploy Server

Other Tools