Skip to main content
Glama

Close browser

browser_close

Closes the shared browser and frees resources while keeping cookies and the persistent profile on disk; logins survive, and it relaunches on next open.

Instructions

Close the shared browser and free its resources. Cookies and the persistent profile stay on disk, so logins survive. It relaunches automatically on the next browser_open. Use this when you are finished with a browser session or want a clean start.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_close"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that cookies and the persistent profile stay on disk, that logins survive, and that the browser auto-relaunches. It does not state what happens if no browser is currently running or whether in-flight operations are cancelled.

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?

Three short sentences with the action and its resource effect front-loaded, followed by persistence semantics and then the usage cue. Nothing is redundant and no sentence could be dropped without losing information.

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 zero-parameter, no-output-schema tool, the description covers the essentials: effect, state persistence, relaunch behavior, and when to call it. Only edge-case behavior (calling when nothing is open) is left unspecified.

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 takes zero parameters and the schema is empty, so there is nothing to disambiguate; baseline 4 applies. The description correctly implies the action is global rather than scoped to a tab or session identifier.

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 gives a specific verb and resource ("Close the shared browser") plus the effect ("free its resources"), which is clearly distinct from the open/act/extract siblings. An agent can tell this is the teardown counterpart to browser_open without inspecting the schema.

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?

It states a clear trigger: "when you are finished with a browser session or want a clean start," and names the follow-on tool ("relaunches automatically on the next browser_open"). It stops short of explicit when-not guidance, e.g., that closing is unnecessary merely to clear cookies since the profile persists.

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