Skip to main content
Glama
nex-browser

NexBrowser MCP Server

Official
by nex-browser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

nex_browser_move_to_group

Moves one or more browser windows into a target window group, or out of any group when groupId is 0, without closing running windows.

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

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
windowIdsNoAlias of windowId

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2026.10.24
    • changedInput schema / properties / windowIds / description
      Previous value: -"Documented alias of windowId"New value: +"Alias of windowId"
  2. 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"
+]
  3. Addedv2026.8.14

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that groups are metadata and windows stay running (non-disruptive, no close/reopen cycle), but says nothing about required permissions, what happens with an unknown groupId or invalid window ID, or how the result is reported.

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?

Three short sentences, front-loaded with the action and the special case, then the operational reassurance. Nothing is redundant or padded.

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

Completeness3/5

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

For a 3-param mutation tool with no annotations and no output schema, it covers the main semantics but leaves a real ambiguity: windowId/windowIds are optional in the schema while the description says 'one or more windows', so it is unclear what happens if they are omitted. Return behavior and error cases are also unaddressed.

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%, so both groupId and windowId/windowIds are already documented, including the groupId=0 semantics and the alias relationship. The description largely restates those facts ('pass groupId=0') and adds only the 'one or more windows' framing, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource: moving NexBrowser windows into a window group, with the groupId=0 special case spelled out. It is distinguishable from group_modify/group_delete, but it never explicitly contrasts itself with those siblings, so a 4 rather than a 5.

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 states a concrete usage condition (groupId=0 removes windows from any group) and reassures that running windows need not be closed first, which is the key decision point. It gives no explicit when-not-to-use or pointer to an alternative tool for a different kind of move.

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