MCP Browser Screenshot Server

browser_close

Terminate the automated browser session to free system resources after completing web page screenshot capture and testing operations.

Instructions

Close the browser instance

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/index.ts:251-265 (handler)

Handler for the browser_close tool: closes the Puppeteer browser instance if it exists and resets the browserState.

case 'browser_close': {
  if (browserState.browser) {
    await browserState.browser.close();
    browserState.browser = null;
    browserState.page = null;
  }
  return {
    content: [
      {
        type: 'text',
        text: 'Browser closed',
      },
    ],
  };
}

src/index.ts:132-139 (registration)
Registration of the browser_close tool in the tools list, specifying name, description, and input schema (empty object).
```
{
  name: 'browser_close',
  description: 'Close the browser instance',
  inputSchema: {
    type: 'object',
    properties: {},
  },
},
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 18, 2025

TDQS

A3.6/5.0

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. It only states the action without noting side effects like session termination, unsaved data loss, or irreversibility. This is minimal but not misleading.

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 sentence that is direct and front-loaded with the verb 'close'. There is no wasted content, making it highly concise.

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

Completeness4/5

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

For a simple close action, the description is adequate, but it could note that it permanently ends the browser session. The lack of behavioral caveats slightly reduces completeness, though no output schema exists to explain return values.

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 accepts zero parameters, and the input schema confirms an empty object. Since there are no parameters, the description does not need to add parameter details, and the baseline for 0 params is 4.

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 uses a specific verb 'close' and resource 'browser instance', clearly distinguishing it from sibling tools like browser_init and navigate. It unambiguously states the tool's function.

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?

No guidance is provided on when to use this tool, such as as a cleanup step after automation completes. There is no mention of alternatives, prerequisites, or exclusions.

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

Deploy Server