Skip to main content
Glama
Sign In
open-browser-control

open-browser-control

by smankoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_new_tab_group

Create a named tab group to organize browsing by task. New tabs and navigations occur within the active group, keeping related pages together.

Instructions

Create a new named tab group for a task. Use this to organize browsing by task — each group gets a label visible in Chrome. The new group becomes the active group; new tabs and navigations happen inside it.

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": {
      "name": "<name>"
    },
    "name": "browser_new_tab_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL to open in the first tab (default: about:blank)
nameYesShort task name for the tab group (e.g. "Search flights", "Debug login")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Discloses that the new group becomes active and subsequent tabs/navigations happen inside it, adding important context beyond schema. No annotations present.

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?

Two focused sentences with no unnecessary words. Key information is front-loaded.

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?

Given no output schema, description explains behavioral outcome (active group, subsequent actions). Parameter details are clear, and overall provides enough for the tool's simplicity.

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?

Schema coverage is 100%, baseline 3. Description adds meaning by explaining name as 'Short task name' and url defaults, and that group gets a visible label, improving agent understanding.

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 uses specific verb 'Create', resource 'named tab group', and context 'for a task', clearly distinguishing it from browser_new_tab which creates a single 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?

Explicitly says 'Use this to organize browsing by task', implying context. Does not state explicit alternatives, but sibling tools are few and distinct.

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

Deploy Server

Other Tools