Skip to main content
Glama
nex-browser

NexBrowser MCP Server

Official
by nex-browser
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

nex_browser_group_delete

Destructive

Delete a custom window group from the active browser workspace. Windows inside the group remain intact and become ungrouped; the default ungrouped bucket 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoDocumented alias of groupId
groupIdNoCustom group ID to delete; the ungrouped bucket 0 is rejected

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
-]
  2. Addedv2026.8.14

TDQS

A4.5/5.0
Behavior5/5

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

The destructiveHint annotation is consistent with 'Delete', and the description goes beyond it by revealing that windows inside the group are not deleted but ungrouped, and that groupId 0 cannot be deleted. This gives the agent essential knowledge about side effects and invalid targets beyond what annotations alone convey.

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?

Two sentences contain the core action, the side effect, and the key exclusions. The main verb and object are front-loaded, with no redundant or filler content.

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

Completeness5/5

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

For a simple two-parameter tool with a destructiveHint annotation and no output schema, the description covers the essential prerequisites: the operation applies to the active workspace, the group must be custom, and groupId 0 is forbidden. No critical calling information is missing.

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%, with both id and groupId already documented in the input schema. The description only restates the groupId=0 limitation ('ungrouped bucket (groupId 0) cannot be deleted') which is already in the schema, so no additional parameter meaning is provided. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Delete one custom window group from the active NexBrowser workspace.' It distinguishes this tool from sibling group operations by clarifying the side effect ('windows inside it are not deleted; they become ungrouped') and excluding groupId 0. This makes the purpose unambiguous.

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?

Clear context is provided: the tool operates on a custom window group in the active workspace, and the ungrouped bucket (groupId 0) is explicitly excluded. It does not explicitly name alternatives such as nex_browser_group_modify or nex_browser_move_to_group, but the behavioral notes make the tool's applicability apparent.

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