Skip to main content
Glama

browser_close

Close a browser instance to free system resources and manage concurrent sessions in the browser pool.

Instructions

Close browser

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:360-365 (registration)
    Registration of the 'browser_close' tool using server.tool().
    server.tool('browser_close', 'Close browser', {},
      async (args) => {
        const result = await proxyToolCall('browser_close', args);
        hasActivePage = false; // Mark page as inactive after close
        return result;
      });
  • The handler function for 'browser_close' that calls proxyToolCall and updates the local state.
    async (args) => {
      const result = await proxyToolCall('browser_close', args);
      hasActivePage = false; // Mark page as inactive after close
      return result;
    });
Behavior2/5

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

With no annotations provided, the description carries full disclosure burden but reveals nothing about behavioral traits: whether closing is destructive (session/cookies lost), if it affects pooled resources, graceful shutdown timing, or tab disposal behavior. 'Close browser' names the action without operational context.

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?

Extremely brief (two words) and front-loaded, but crosses into under-specification. While no words are wasted, the brevity fails to meet the informational needs for a destructive/terminal operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given low structural complexity (0 params, no output schema, no annotations), requirements are minimal. However, for a session-terminating operation, the description omits critical context about resource cleanup and subsequent tool availability (e.g., whether browser_navigate would fail afterward).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema contains zero parameters, establishing baseline score of 4. With no parameters requiring semantic clarification, the description neither adds value nor creates deficits in this dimension.

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

Purpose2/5

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

The description 'Close browser' is tautological, simply converting the tool name 'browser_close' into words. While it identifies the verb and resource, it fails to distinguish from siblings (e.g., browser_tabs) or clarify scope (entire browser vs. specific windows).

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 guidance provided on when to invoke this versus leaving the browser open, what prerequisites exist (e.g., an active browser session), or the consequences of closing. Lacks explicit when/when-not directives entirely.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OMGEverdo/browser-pool-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server