Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_group_modify

Rename or reorder a custom window group in the active NexBrowser workspace, keeping group names unique; the ungrouped bucket cannot be changed.

Instructions

Rename or reorder one custom window group in the active NexBrowser workspace. Group names must stay unique inside the team. The ungrouped bucket (groupId 0) cannot be changed.

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

Input Schema

NameRequiredDescriptionDefault
idNoAlias of groupId
seqNoNew sort order
nameNoNew unique group name
groupIdNoCustom group ID to rename or reorder; the ungrouped bucket 0 is rejected

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

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that this is a mutation operation, enforces name uniqueness, and rejects groupId 0. However, it does not explain permission requirements, whether partial updates are allowed, what happens if no update fields are supplied, or what the response looks like.

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 three short sentences with no wasted wording. The primary operation is front-loaded, and the constraints follow in a logical order.

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?

The description is adequate for a group-modification tool, but since all four parameters are optional and no annotations or output schema exist, it should clarify that at least one of name or seq is needed and what happens when neither is supplied. It also omits return behavior, though that is less critical without an output 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 schema already documents id, seq, name, and groupId. The description reinforces the uniqueness constraint and the groupId 0 rejection, but adds little beyond what the schema already provides for parameter meaning.

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 states a specific verb pair (rename or reorder) and a precise resource (one custom window group in the active NexBrowser workspace). It clearly differentiates the tool from sibling group operations such as create, list, delete, and move_to_group.

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 explicit constraints: group names must be unique within the team, and the ungrouped bucket with groupId 0 cannot be changed. It does not explicitly name sibling alternatives, but the intended usage context is clear enough for an agent to select it correctly.

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