Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_move_to_group

Move one or more NexBrowser windows into a specified window group, or pass groupId=0 to move them out without closing the 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.

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

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. Changed4 schema fields changedv2026.11.3
    • removedInput schema / properties / groupId / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / groupId / type
      Added value: +[
      +  "string",
      +  "number"
      +]
    • changedInput schema / properties / windowId / anyOf
      Previous value: -[
      -  {
      -    "anyOf": [
      -      {
      -        "type": "string"
      -      },
      -      {
      -        "type": "number"
      -      }
      -    ]
      -  },
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "number"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": [
      +      "string",
      +      "number"
      +    ]
      +  },
      +  {
      +    "items": {
      +      "type": [
      +        "string",
      +        "number"
      +      ]
      +    },
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / windowIds / anyOf
      Previous value: -[
      -  {
      -    "anyOf": [
      -      {
      -        "type": "string"
      -      },
      -      {
      -        "type": "number"
      -      }
      -    ]
      -  },
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "number"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": [
      +      "string",
      +      "number"
      +    ]
      +  },
      +  {
      +    "items": {
      +      "type": [
      +        "string",
      +        "number"
      +      ]
      +    },
      +    "type": "array"
      +  }
      +]
  2. Changed1 schema field changedv2026.10.24
    • changedInput schema / properties / windowIds / description
      Previous value: -"Documented alias of windowId"New value: +"Alias of windowId"
  3. 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"
      +]
  4. Addedv2026.8.14

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description does most of the essential work: it discloses that groups are metadata and windows can be moved while running, plus the special groupId=0 ungrouping behavior. It leaves out error behavior for an invalid group ID, idempotency, and whether changes are reversible, which matter for a mutation tool with no annotation safety profile.

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 core action, then the special-case value, then the rationale. Every sentence adds information and nothing is redundant.

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?

For a three-parameter mutation tool with no output schema, the description covers the action, the ungrouping case, and the key non-destructive property. It is nearly complete; only failure modes and any preconditions are absent.

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 schema already explains groupId, windowId, windowIds and the groupId=0 convention. The description restates the groupId=0 case but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Move') and resource ('NexBrowser windows into a window group'), which clearly separates it from the sibling group tools (group_list, group_create, group_modify, group_delete). An agent can identify the operation without opening the schema.

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

Usage Guidelines3/5

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

The description implies when to use it (to group windows or ungroup them via groupId=0) and notes that running windows need not be closed. It does not explicitly route against alternatives such as nex_browser_group_create/modify, nor does it state prerequisites like the window needing to exist or be connected.

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