Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_group_delete

Destructive

Delete a custom window group by ID from the active NexBrowser workspace; its windows remain open and become ungrouped, while group 0 cannot be deleted.

Instructions

Delete one custom window group from the active NexBrowser workspace. The windows inside it are not deleted; they become ungrouped. The ungrouped bucket (groupId 0) cannot be deleted.

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_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAlias of groupId
groupIdNoCustom group ID to delete; 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. Changed2 schema fields changedv2026.8.20
    • addedInput schema / properties / id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    }
      +  ],
      +  "description": "Documented alias of groupId"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "groupId"
      -]
  4. Addedv2026.8.14

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare destructiveHint=true, so the description's key contribution is the blast-radius detail: the windows inside are not deleted but become ungrouped. That is exactly the context an agent needs before a destructive call. It does not state whether the group deletion itself is irreversible or what an invalid ID returns, but the central mutation behavior is disclosed.

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 with the action first, followed by consequence and constraint. Nothing is redundant and no sentence could be dropped without losing information.

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 two-parameter destructive delete with full schema coverage and no output schema, the description covers the essential effect and the one hard constraint. A note on error behavior or irreversibility would close the remaining 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 both parameters are documented in the schema, including the groupId 0 rejection. The description's mention of the ungrouped bucket and 'custom' group IDs reinforces but does not add syntax or format detail beyond the schema; it also never mentions the 'id' alias. Baseline 3 applies.

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?

States a specific verb and resource ('Delete one custom window group') and scopes it to the active NexBrowser workspace. The verb alone separates it from the sibling group tools (group_list, group_create, group_modify), though no sibling is named explicitly.

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?

Provides a clear use context (removing a custom group from the workspace) and an explicit exclusion: the ungrouped bucket (groupId 0) cannot be deleted. It stops short of saying what to do instead when a group must be emptied first, or naming an alternative 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