Skip to main content
Glama

close_browser

Close the active browser instance to free system resources and end automation sessions. This tool terminates browser processes controlled through the Chrome DevTools Protocol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:91-99 (registration)
    Registers the 'close_browser' MCP tool with an empty input schema. The inline handler function closes the global Playwright browser instance if it exists, resets the associated page and CDP session variables to null, and returns a confirmation message in the expected MCP response format.
    server.tool("close_browser", {}, async () => {
      if (browser) {
        await browser.close();
        browser = null;
        page = null;
        cdp = null;
      }
      return { content: [{ type: "text", text: "Browser closed" }] };
    });
  • server.js:91-99 (handler)
    The handler function for the 'close_browser' tool. It checks if a browser instance exists (global variable), closes it using Playwright's browser.close(), resets the browser, page, and cdp globals to null, and returns a structured MCP response confirming the action.
    server.tool("close_browser", {}, async () => {
      if (browser) {
        await browser.close();
        browser = null;
        page = null;
        cdp = null;
      }
      return { content: [{ type: "text", text: "Browser closed" }] };
    });
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/Myestery/browser-cdp-mcp'

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