Playwright MCP

browser_close

Destructive

Close the current browser page in Playwright MCP to manage browser automation sessions and free system resources.

Instructions

Close the page

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/tools/common.ts:31-35 (handler)
Handler implementation for the browser_close tool. Closes the browser context and instructs to include tabs in response with a code snippet to close the page.
```
handle: async (context, params, response) => {
  await context.closeBrowserContext();
  response.setIncludeTabs();
  response.addCode(`await page.close()`);
},
```
src/tools/common.ts:24-29 (schema)
Input/output schema definition for the browser_close tool. No input parameters required, marked as readOnly.
```
  name: 'browser_close',
  title: 'Close browser',
  description: 'Close the page',
  inputSchema: z.object({}),
  type: 'readOnly',
},
```

src/tools.ts:17-37 (registration)

Imports the common tools module (containing browser_close) and registers it by spreading into the allTools export array used by the MCP server backend.

import common from './tools/common.js';
import console from './tools/console.js';
import dialogs from './tools/dialogs.js';
import evaluate from './tools/evaluate.js';
import files from './tools/files.js';
import install from './tools/install.js';
import keyboard from './tools/keyboard.js';
import navigate from './tools/navigate.js';
import network from './tools/network.js';
import pdf from './tools/pdf.js';
import snapshot from './tools/snapshot.js';
import tabs from './tools/tabs.js';
import screenshot from './tools/screenshot.js';
import wait from './tools/wait.js';
import mouse from './tools/mouse.js';

import type { Tool } from './tools/tool.js';
import type { FullConfig } from './config.js';

export const allTools: Tool<any>[] = [
  ...common,

Tool Definition Quality

A3.6/5.0

Behavior4/5

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

The description 'Close the page' aligns with the destructiveHint=true annotation, indicating it terminates the page. It adds context beyond annotations by specifying what gets closed (the page), though it doesn't detail side effects like potential data loss or if it affects other tabs. No contradiction with annotations exists.

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 extremely concise at just three words, front-loading the essential action without any fluff. Every word ('Close the page') directly contributes to understanding the tool's function, making it highly efficient.

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 (0 parameters, destructive operation) and lack of output schema, the description is minimally adequate. It states the action but doesn't cover behavioral nuances like confirmation dialogs or post-closure state, which could be helpful for an agent in a browser automation context.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description doesn't need to explain parameters, and it appropriately doesn't add unnecessary details, maintaining clarity for a parameterless tool.

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 'Close the page' clearly states the action (close) and target (the page), making the purpose immediately understandable. However, it doesn't distinguish this from potential sibling tools like browser_tabs (which might manage multiple tabs) or explicitly mention it closes the current browser page versus other browser 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't specify if this should be used after completing tasks, to clean up resources, or in what context it's appropriate compared to other browser navigation tools like browser_navigate or browser_tabs.

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

Install Server

Latest Blog Posts

Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security
Open Source Has a Bot Problem
By punkpeye on March 19, 2026.
open source

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/nzjami/mcpPlaywright'

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