Skip to main content
Glama

Close a browser session

browser_close
Destructive

Use for: ending a session and freeing its browser. Sessions also expire automatically after 10 idle minutes. Free on every door — closing is never charged. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
session_idYesSession ID. Reuse the same ID to keep cookies, login state and page position across calls; a new ID starts a fresh browser.

Output Schema

NameRequiredDescriptionDefault
closedYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds non-obvious context beyond them: the browser is freed, idle sessions self-expire after 10 minutes, and closing is never billed. That billing and lifecycle context is genuinely useful. It stops short of 5 because it doesn't state whether cookies/login state survive or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and idle-expiry facts are well front-loaded, but 'Free on every door — closing is never charged. Free.' states the same billing point three times in one short description, which is noticeable waste. Trimming to a single clause would make the rest stronger.

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?

With one fully documented parameter, an output schema, and complete annotations, the description only needs to add purpose and lifecycle context — both are present. The remaining gap is what state survives a close, but the output schema and annotation set cover enough that this is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the session_id description already explains ID reuse semantics in detail. The tool description adds nothing about the parameter, so the baseline of 3 applies when the schema does all the work.

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 leads with 'Use for: ending a session and freeing its browser', a specific verb and resource that is clearly distinct from every sibling (navigate, act, extract, screenshot, snapshot). It doesn't explicitly contrast against a sibling, but none of the listed siblings could be confused with this.

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 'Use for:' framing gives an explicit trigger, and the note that 'Sessions also expire automatically after 10 idle minutes' implicitly tells the agent that closing is optional for cleanup. There is no explicit when-not guidance beyond that hint, and no named alternative, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources