Skip to main content
Glama

playwright_close

Automatically close the browser and release all resources to optimize system performance after completing browser automation tasks using the MCP server.

Instructions

Close the browser and release all resources

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary handler logic for the 'playwright_close' tool. Closes the Playwright browser instance if it exists, handles errors, resets global browser state, and returns a success message.
    if (name === "playwright_close") {
      if (browser) {
        try {
          if (browser.isConnected()) {
            await browser.close().catch(e => console.error("Error closing browser:", e));
          }
        } catch (error) {
          console.error("Error during browser close in handler:", error);
        } finally {
          resetBrowserState();
        }
        return {
          content: [{
            type: "text",
            text: "Browser closed successfully",
          }],
          isError: false,
        };
      }
      return {
        content: [{
          type: "text",
          text: "No browser instance to close",
        }],
        isError: false,
      };
    }
  • Tool schema definition including name, description, and empty input schema for 'playwright_close'.
      name: "playwright_close",
      description: "Close the browser and release all resources",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • CloseBrowserTool class providing alternative implementation for closing the browser. Instantiated but bypassed due to inline handler in toolHandler.ts.
    export class CloseBrowserTool extends BrowserToolBase {
      /**
       * Execute the close browser tool
       */
      async execute(args: any, context: ToolContext): Promise<ToolResponse> {
        if (context.browser) {
          try {
            // Check if browser is still connected
            if (context.browser.isConnected()) {
              await context.browser.close().catch(error => {
                console.error("Error while closing browser:", error);
              });
            } else {
              console.error("Browser already disconnected, cleaning up state");
            }
          } catch (error) {
            console.error("Error during browser close operation:", error);
            // Continue with resetting state even if close fails
          } finally {
            // Always reset the global browser and page references
            resetBrowserState();
          }
          
          return createSuccessResponse("Browser closed successfully");
        }
        
        return createSuccessResponse("No browser instance to close");
      }
    }
  • src/tools.ts:450-473 (registration)
    'playwright_close' listed in BROWSER_TOOLS array used for conditional browser launch logic.
    export const BROWSER_TOOLS = [
      "playwright_navigate",
      "playwright_screenshot",
      "playwright_click",
      "playwright_iframe_click",
      "playwright_iframe_fill",
      "playwright_fill",
      "playwright_select",
      "playwright_hover",
      "playwright_upload_file",
      "playwright_evaluate",
      "playwright_close",
      "playwright_expect_response",
      "playwright_assert_response",
      "playwright_custom_user_agent",
      "playwright_get_visible_text",
      "playwright_get_visible_html",
      "playwright_go_back",
      "playwright_go_forward",
      "playwright_drag",
      "playwright_press_key",
      "playwright_save_as_pdf",
      "playwright_click_and_switch_tab"
    ];
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions releasing resources, which adds useful context beyond the basic 'close' action, but does not detail side effects like terminating all open pages or whether the browser can be reopened. It adequately describes the core behavior but lacks depth on operational implications.

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, direct sentence with no wasted words, clearly front-loading the main action. Every part of the sentence ('Close the browser and release all resources') contributes essential information, making it highly concise and well-structured.

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 the tool's simplicity (no parameters, no output schema, no annotations), the description is complete enough for basic understanding but could benefit from more context, such as typical usage patterns or effects on sibling tools. It covers the core action but leaves gaps in practical guidance.

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 tool has zero parameters, and the schema description coverage is 100%, so no parameter information is needed. The description appropriately avoids discussing parameters, making it efficient and focused on the tool's purpose without unnecessary 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 clearly states the specific action ('Close') and target resource ('the browser'), distinguishing it from sibling tools like playwright_screenshot or playwright_get that perform different operations. It precisely defines what the tool does without being tautological.

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, such as whether it should be called at the end of a session or in specific cleanup scenarios. There are no explicit when/when-not instructions or references to sibling tools for context.

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

Related 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/executeautomation/mcp-playwright'

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