Skip to main content
Glama
seabassgonzalez

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
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • 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: {},
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose important behavioral aspects: whether this requires an existing browser instance, what happens to open tabs/data, whether it's synchronous/asynchronous, or any error conditions. For a potentially destructive operation with zero annotation coverage, this is insufficient.

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 states exactly what the tool does with zero wasted words. It's appropriately sized for a simple tool with no parameters and gets straight to the point.

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, no output schema), the description is minimally complete but lacks important context for a potentially destructive operation. Without annotations or output schema, the description should address more behavioral aspects like prerequisites, effects, and error handling to be fully complete.

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 with 100% schema description coverage, so the baseline is 4. The description doesn't need to explain parameters, and it correctly doesn't mention any. No parameter information is missing or misleading.

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 'Close the browser instance' clearly states the specific action (close) and target resource (browser instance). It distinguishes from siblings like browser_launch (opposite action) and browser_navigate (different browser operation). The verb+resource combination is unambiguous.

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

Usage Guidelines4/5

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

The description implies usage context - this tool should be used when a browser instance needs to be terminated. It doesn't explicitly state when NOT to use it or name alternatives, but the context is clear enough given the sibling tools. No misleading guidance is present.

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/seabassgonzalez/mcp-browser-screenshot'

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