Skip to main content
Glama
Sign In
Chrome Bridge

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_tab

Opens a new tab in Chrome, optionally at a URL, and sets it as the target for later commands. Supports background tabs and new windows.

Instructions

Open a new tab, optionally at a URL, and make it the implicit target of later commands in this session. Each call creates another tab: reuse a tab_id or navigate() to move an existing one instead of piling up tabs.

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": "create_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoWindow y (new_window)
urlNoURL to open (default: new tab page)
leftNoWindow x on the virtual desktop (new_window)
widthNoWindow width px (new_window)
activeNofalse opens the tab in the background, leaving the current one focused
heightNoWindow height px (new_window)
new_windowNoOpen in a fresh window instead of a tab; with left/top it lands on the chosen monitor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.15.0
    • addedInput schema / properties / height
      Added value: +{
+  "description": "Window height px (new_window)",
+  "type": "number"
+}
    • addedInput schema / properties / left
      Added value: +{
+  "description": "Window x on the virtual desktop (new_window)",
+  "type": "number"
+}
    • addedInput schema / properties / new_window
      Added value: +{
+  "default": false,
+  "description": "Open in a fresh window instead of a tab; with left/top it lands on the chosen monitor",
+  "type": "boolean"
+}
    • addedInput schema / properties / top
      Added value: +{
+  "description": "Window y (new_window)",
+  "type": "number"
+}
    • addedInput schema / properties / width
      Added value: +{
+  "description": "Window width px (new_window)",
+  "type": "number"
+}
  2. Changed1 schema field changedv1.10.0
    • addedInput schema / properties / active / description
      Added value: +"false opens the tab in the background, leaving the current one focused"
  3. First observedv1.8.0

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses that the new tab becomes 'the implicit target of later commands in this session' and that each call creates another tab, behaviors not captured by the annotations. This provides critical context about statefulness and side effects beyond the structured hints.

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 sentences, front-loaded with the primary action and followed by a practical usage tip. Every sentence contributes value with no redundancy.

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?

The description is fully self-contained for a state-changing tool: it explains the action, the session-wide implication, and the fallback to navigate(). It does not explicitly state the return value, but the mention of 'reuse a tab_id' implies a tab identifier is returned, which is sufficient given the tool's simplicity and the comprehensive schema.

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 description coverage is 100%, so the baseline is 3. The description adds minimal parameter-specific meaning beyond the schema, merely mentioning the optional URL, which is already documented. It does not introduce new information about parameters.

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 a specific verb ('Open') and resource ('new tab'), clearly distinguishing this from navigation tools. It explicitly contrasts with navigate(), stating 'reuse a tab_id or navigate() to move an existing one instead of piling up tabs.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance: it tells the agent that each call creates a new tab and recommends reusing a tab_id or using navigate() to move an existing tab, preventing tab accumulation. This addresses when to use the tool versus alternatives.

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