Skip to main content
Glama
devskido

Playwright MCP Server

by devskido

playwright_close

Close the browser and release all resources after completing web automation tasks with Playwright.

Instructions

Close the browser and release all resources

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary handler execution for the 'playwright_close' tool. This special case handles closing the browser instance, resetting global state, and returning appropriate success/error messages. Executed directly in handleToolCall before other logic.
    // Special case for browser close to ensure it always works
    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: [],
      },
    },
  • src/tools.ts:450-473 (registration)
    Registration of 'playwright_close' in BROWSER_TOOLS array, used by toolHandler to determine browser initialization needs.
    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"
    ];
  • Alternative handler implementation in CloseBrowserTool.execute method. Closely mirrors the primary handler logic. Class is instantiated but not invoked for this tool due to special case handling.
    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");
      }
    }
  • Lists 'playwright_close' among browser tools for export/reference.
    "playwright_close",
Behavior2/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 'release all resources', which hints at cleanup, but doesn't specify whether this is destructive (e.g., closes all tabs, ends sessions), irreversible, or has side effects like terminating ongoing operations. More detail on behavioral traits is needed for a mutation tool.

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, efficient sentence that front-loads the key action ('Close the browser') and adds a clarifying detail ('release all resources'). Every word earns its place with no waste.

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 complexity (a mutation with no parameters) and lack of annotations or output schema, the description is minimally adequate. It states what the tool does but doesn't fully cover behavioral aspects like effects or prerequisites, leaving gaps in completeness for 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 tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter explanation in the description. The baseline for this scenario is 4, as the description appropriately doesn't add unnecessary param details.

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 clearly states the action ('Close') and the resource ('the browser'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'end_codegen_session' or 'clear_codegen_session', which might also involve cleanup operations, so it doesn't reach the highest score.

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 when to close the browser versus keeping it open for other operations, or how it relates to session management tools like 'end_codegen_session'. It lacks explicit context or exclusions.

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/devskido/customed-playwright'

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