Skip to main content
Glama
nex-browser

NexBrowser MCP Server

Official
by nex-browser
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

nex_browser_move_to_group

Move one or more running browser windows into a specified window group, or use groupId 0 to remove them from any group.

Instructions

Move one or more NexBrowser windows into a window group. Pass groupId=0 to move them out of any group. Groups are window metadata, so running windows can be moved without closing them first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYesTarget group ID from nex_browser_group_list; 0 moves the windows out of any group
windowIdNoOne window ID or a list of window IDs; alias of windowIds
windowIdsNoDocumented alias of windowId

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2026.8.20
    • changedInput schema / properties / windowId / description
      Previous value: -"One window ID or a list of window IDs"New value: +"One window ID or a list of window IDs; alias of windowIds"
    • addedInput schema / properties / windowIds
      Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        }
+      ]
+    },
+    {
+      "items": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "number"
+          }
+        ]
+      },
+      "type": "array"
+    }
+  ],
+  "description": "Documented alias of windowId"
+}
    • changedInput schema / required
      Previous value: -[
-  "windowId",
-  "groupId"
-]New value: +[
+  "groupId"
+]
  2. Addedv2026.8.14

TDQS

A4.4/5.0
Behavior4/5

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

Without annotations, the description discloses key behavioral aspects: the operation is non-destructive (windows remain running) because groups are metadata. It does not mention potential side effects, error conditions, or whether the operation is synchronous, but the core behavior is transparently described.

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, using two sentences without fluff. It front-loads the main purpose and then provides essential context about the metadata nature and the groupId=0 case.

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 simple operation, the description covers the essential usage and behavior. It lacks explicit mention of what happens if no windowId is provided, but the phrase 'one or more' implies specification is required. The absence of an output schema makes return value explanation unnecessary.

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?

The schema already describes all parameters with 100% coverage, including the alias relationship between windowId and windowIds. The description reinforces the groupId=0 special case, though this is already in the schema. The semantics are clear and consistent.

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 tool's purpose: moving one or more NexBrowser windows into a window group. It specifies the action (move), the resource (windows), and the target (group), distinguishing it from other window operations.

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 provides specific usage guidance by mentioning the groupId=0 condition for moving windows out of a group. It also explains that groups are metadata, so the move can happen without closing windows, which informs when this operation is appropriate. However, it does not explicitly compare to alternative tools or state when not to use it.

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