Skip to main content
Glama

browser_reset_sessions

browser_reset_sessions
DestructiveIdempotent

End a browser task by releasing the conversation's session and ungrouping its tabs; optionally close only tabs it opened, never tabs the user already had open.

Instructions

Finish a browser task: release this conversation's session and ungroup its tabs so the group does not linger in the user's tab bar. It also closes the tabs this conversation opened itself, but never a tab the user already had open, so pass close_opened_tabs: false to keep them. force: true instead releases every session, including other conversations', and only ungroups.

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_reset_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoAlso release sessions other conversations still hold. Default false.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.
close_opened_tabsNoAlso close the tabs this conversation opened itself. A tab the user already had open is never closed. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructive=true and idempotent=true; the description adds real substance on top: exactly what is destroyed (only tabs this conversation opened, never pre-existing user tabs), what force does to other conversations' sessions, and that force only ungroups rather than closing tabs. That is precisely the blast-radius information an agent needs before a destructive call.

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

Conciseness4/5

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

Two dense sentences with the core action and the safety guarantee front-loaded, and no filler. The trailing clause "and only ungroups" after force: true is terse enough to be slightly ambiguous on first read, costing a point.

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 destructive, zero-required-parameter cleanup tool with no output schema, the description covers scope, defaults, and the cross-conversation effect of force. Only minor gaps remain, such as whether force ignores close_opened_tabs and what the agent should expect after reset.

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%, so each parameter is already documented in the input schema. The description restates the close_opened_tabs and force semantics in behavioral terms rather than adding format or precedence detail beyond the schema (it does not clarify how session_id interacts with force, for example). Baseline 3 is appropriate.

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?

States a specific verb and resource — release this conversation's session and ungroup its tabs — and frames it as the task-finishing operation. The closing behavior is scoped explicitly ("closes the tabs this conversation opened itself, but never a tab the user already had open"), which separates it clearly from per-tab siblings like browser_close_tab.

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?

Gives a clear when-to-use frame ("Finish a browser task") and explains the two mode switches: close_opened_tabs: false keeps tabs, force: true escalates to all sessions. It does not name a sibling alternative such as browser_close_tab for single-tab cleanup, so the guidance is clear but not fully comparative.

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