Skip to main content
Glama
cloudflare

Cloudflare Playwright MCP

Official
by cloudflare

browser_close

Read-only

Automatically close web pages during browser automation to manage resources efficiently using Cloudflare Playwright MCP's browser control capabilities.

Instructions

Close the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'browser_close' tool. It closes the current browser context and returns a code snippet simulating 'await page.close()' with flags to disable snapshot and network wait.
    handle: async context => {
      await context.close();
      return {
        code: [`await page.close()`],
        captureSnapshot: false,
        waitForNetwork: false,
      };
    },
  • Schema definition for the 'browser_close' tool, specifying name, title, description, empty input schema, and readOnly type.
    schema: {
      name: 'browser_close',
      title: 'Close browser',
      description: 'Close the page',
      inputSchema: z.object({}),
      type: 'readOnly',
    },
  • Tool registration using defineTool, which defines the 'browser_close' tool with its schema and handler.
    const close = defineTool({
      capability: 'core',
    
      schema: {
        name: 'browser_close',
        title: 'Close browser',
        description: 'Close the page',
        inputSchema: z.object({}),
        type: 'readOnly',
      },
    
      handle: async context => {
        await context.close();
        return {
          code: [`await page.close()`],
          captureSnapshot: false,
          waitForNetwork: false,
        };
      },
    });
  • Export of the tools array including the 'close' (browser_close) tool for registration in the MCP tools system.
    export default (captureSnapshot: boolean) => [
      close,
      resize(captureSnapshot)
    ];
Behavior3/5

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

Annotations indicate readOnlyHint=true and destructiveHint=false, suggesting a safe operation, but the description adds no behavioral context beyond 'Close the page'. It doesn't clarify what 'close' entails (e.g., if it terminates a session, affects other tabs, or requires confirmation), missing details that annotations don't cover, though it doesn't contradict them.

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 with 'Close the page', a single sentence that directly conveys the core action without any wasted words. It's front-loaded and efficient, making it easy to parse quickly.

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, annotations covering safety), the description is minimally adequate but lacks depth. Without an output schema, it doesn't explain what happens after closing (e.g., success confirmation or error handling), and it misses context about interactions with sibling tools, leaving gaps in understanding.

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 coverage, the input schema fully documents the lack of inputs. The description doesn't need to add parameter details, so it meets the baseline for a tool with no parameters, though it doesn't explicitly state 'no parameters required'.

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), which is specific and unambiguous. However, it doesn't differentiate from sibling 'browser_tab_close', which appears to serve a similar function for tabs rather than pages, leaving some ambiguity about the exact scope.

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 like 'browser_tab_close' or other browser control tools. It lacks context about prerequisites (e.g., needing an open page) or exclusions, offering minimal usage direction.

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

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