Skip to main content
Glama

browser_close

Closes the current browser session to free system resources and end automation tasks in Selenium WebDriver.

Instructions

Close the current browser session

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The inline handler function for the 'browser_close' tool, registered via server.tool(). It retrieves the current driver, quits it, cleans up the session state, and returns a confirmation or error message.
    server.tool('browser_close', 'Close the current browser session', {}, async () => {
      try {
        const driver = stateManager.getDriver();
        await driver.quit();
        const sessionId = stateManager.getCurrentSession();
    
        if (sessionId) {
          stateManager.removeDriver(sessionId);
        }
        stateManager.resetCurrentSession();
    
        return {
          content: [{ type: 'text', text: `Browser session ${sessionId} closed` }],
        };
      } catch (e) {
        return {
          content: [
            {
              type: 'text',
              text: `Error closing session: ${(e as Error).message}`,
            },
          ],
        };
      }
    });
  • The 'browser_close' tool is registered here within the registerBrowserTools function using server.tool(), with no input schema and the handler inline.
    server.tool('browser_close', 'Close the current browser session', {}, async () => {
      try {
        const driver = stateManager.getDriver();
        await driver.quit();
        const sessionId = stateManager.getCurrentSession();
    
        if (sessionId) {
          stateManager.removeDriver(sessionId);
        }
        stateManager.resetCurrentSession();
    
        return {
          content: [{ type: 'text', text: `Browser session ${sessionId} closed` }],
        };
      } catch (e) {
        return {
          content: [
            {
              type: 'text',
              text: `Error closing session: ${(e as Error).message}`,
            },
          ],
        };
      }
    });
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 burden of behavioral disclosure. 'Close the current browser session' implies a destructive operation that ends the session, but it does not specify whether this is reversible, if it requires confirmation, what happens to unsaved data, or if it affects other browser instances. For a tool with zero annotation coverage and clear destructive potential, this is insufficient.

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?

The description is a single, clear sentence with no wasted words. It is front-loaded and efficiently conveys the core action without redundancy or fluff.

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?

Given the tool's complexity (destructive operation with no annotations or output schema), the description is incomplete. It lacks critical context such as effects on browser state, error conditions, or confirmation requirements. For a tool that ends a session, more behavioral detail is needed to guide safe usage.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not mention parameters, which is appropriate. A baseline of 4 is applied as it correctly omits unnecessary parameter details.

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

Purpose5/5

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

The description 'Close the current browser session' clearly states the action (close) and the resource (current browser session). It distinguishes itself from sibling tools like browser_open, browser_navigate, or browser_refresh by specifying termination rather than initiation or navigation of a session.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., requires an open session), consequences (e.g., all windows/tabs close), or when to avoid it (e.g., if data needs saving). Without such context, the agent lacks usage direction.

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/pshivapr/selenium-mcp'

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