Skip to main content
Glama
frsorrentino

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

move_tab

Idempotent

Move an existing tab to another window or into a new popup window, preserving its history and page state. Destination must be a normal browser window.

Instructions

Move an existing tab into another window (chrome.tabs.move), keeping id, history and page state; works on chrome-untrusted:// tabs too. The destination must be a normal window: out of an app/popup window is fine, into one is refused. A ChromeOS Terminal tab can be pulled out (new_window, window_type popup) but never merged back: extensions cannot create app windows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoNew window y (new_window)
leftNoNew window x (new_window)
indexNoPosition in the destination window; -1 appends at the end
widthNoNew window width px (new_window)
heightNoNew window height px (new_window)
tab_idYesTab to move; get it from get_tabs
window_idNoDestination window; get_tabs reports windowId for every tab
new_windowNoExtract the tab into a fresh window instead of an existing one
window_typeNonew_window only: popup has no tab strip nor omnibox, the terminal-window looknormal

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.16.1
    • changedInput schema / properties / new_window / description
      Previous value: -"Extract the tab into a fresh window instead — tabs.move needs an existing window, this does not"New value: +"Extract the tab into a fresh window instead of an existing one"
    • changedInput schema / properties / window_type / description
      Previous value: -"new_window only: popup has no tab strip and no omnibox — the terminal-window look for detached chrome-untrusted://terminal tabs"New value: +"new_window only: popup has no tab strip nor omnibox, the terminal-window look"
  2. Changed7 schema fields changedv1.15.0
    • addedInput schema / properties / height
      Added value: +{
+  "description": "New window height px (new_window)",
+  "type": "number"
+}
    • addedInput schema / properties / left
      Added value: +{
+  "description": "New window x (new_window)",
+  "type": "number"
+}
    • addedInput schema / properties / new_window
      Added value: +{
+  "default": false,
+  "description": "Extract the tab into a fresh window instead — tabs.move needs an existing window, this does not",
+  "type": "boolean"
+}
    • addedInput schema / properties / top
      Added value: +{
+  "description": "New window y (new_window)",
+  "type": "number"
+}
    • addedInput schema / properties / width
      Added value: +{
+  "description": "New window width px (new_window)",
+  "type": "number"
+}
    • addedInput schema / properties / window_type
      Added value: +{
+  "default": "normal",
+  "description": "new_window only: popup has no tab strip and no omnibox — the terminal-window look for detached chrome-untrusted://terminal tabs",
+  "enum": [
+    "normal",
+    "popup"
+  ],
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "tab_id",
-  "window_id"
-]New value: +[
+  "tab_id"
+]
  3. Addedv1.12.0

TDQS

A4.4/5.0
Behavior5/5

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

The description goes beyond the annotations by detailing side effects and edge cases: it preserves id/history/state, works on chrome-untrusted:// tabs, only allows moving into normal windows, and clarifies that ChromeOS Terminal tabs can be pulled out but not merged back. This is extensive behavioral disclosure.

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?

The description is concise yet information-dense, packing all necessary constraints and nuances into two sentences without redundancy or filler. It is well-structured and easy to parse.

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 the complexity of the tool (edge cases, constraints, parameter interactions), the description covers the essential usage rules comprehensively. It does not describe the return value or error behavior, but since there is no output schema and the primary usage context is clear, this is a minor gap.

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 each parameter already has descriptive text in the schema. The main description does not add meaning beyond what the schema provides; it merely references get_tabs for tab_id and window_id, which is already in the schema descriptions. Thus 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?

The description clearly states the action (move an existing tab) and the target resource (into another window), while also providing key constraints (destination must be normal, etc.). It distinguishes itself from sibling tools like get_tabs or create_tab by focusing specifically on moving tabs.

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 description gives concrete usage guidance: it explains where to get the tab_id (from get_tabs) and notes special cases like chrome-untrusted:// and ChromeOS Terminal tabs. However, it does not explicitly contrast with alternative tools (e.g., tab_action) or state when not to use this tool.

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