Skip to main content
Glama
KitchenSink4AI

KitchenSink4Web

Official
by KitchenSink4AI
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

manage_tabs

Manage browser tabs: open, select, close, list tabs, report active tab, and capture popup pages, returning handles for further actions.

Instructions

List, open, select, or close tabs, report which is focused, and capture pages a click opened in a popup. Mints and returns the explicit page handles every other tool accepts, which is how browser state survives across calls without relying on protocol sessions. Closing a page invalidates its refs and its delta read tokens, and the result says so rather than leaving a later failure to explain it. On a session with more than one cookie jar, context says which jar a new tab opens in and every listed page says which jar it belongs to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
pageNo
actionNolist
contextNo
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond readOnlyHint=false, it discloses side effects: it mints page handles, invalidates them on close, and reports invalidation instead of failing later; also notes cookie-jar association.

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?

Four dense sentences, each conveys one essential behavioral fact; no redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, it still describes what is returned (page handles, focused tab, cookie-jar labels, invalidation notices), enough to call and interpret results.

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?

Though the schema has no per-parameter descriptions, the prose maps action to verbs, page to handles, context to cookie jar, and session to browser state; url is implied for open but not named.

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 names the concrete actions (list, open, select, close) and the resource (tabs/pages), and explicitly positions tab management as distinct from navigation/session tools.

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 explains when the tool is needed—any time another tool needs a page handle—and clarifies multi-cookie-jar context selection, but it does not explicitly contrast with sibling tools like navigate or manage_session.

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