Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_bind_account

Destructive

Bind workspace catalog accounts to one or more closed NexBrowser windows, replacing existing bindings; close running windows first before opening and filling accounts.

Instructions

Bind one or more workspace catalog platform accounts to one or more closed NexBrowser windows. This replaces the existing window binding. Pass accountIds=[] to remove it. Running windows are rejected and must be closed first. After opening, use nex_browser_accounts to fill.

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": {
      "accountIds": "<accountIds>"
    },
    "name": "nex_browser_bind_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowIdNoOne window ID or a list of closed window IDs; alias of windowIds
windowIdsNoAlias of windowId
accountIdsYesCatalog account IDs that replace the window binding; [] or 0 removes all bound accounts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2026.11.3
    • changedInput schema / properties / accountIds / 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 / 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. Addedv2026.8.20

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only flag destructiveHint=true; the description adds the crucial detail of what is destroyed (the existing window binding is replaced), how to undo it (empty accountIds), and the rejection rule for running windows. It does not state auth/permission requirements or whether partial failures across multiple windows roll back, which keeps it short of a 5.

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?

Four short sentences, front-loaded with the core action, then side effect, then removal, then precondition, then next step. No filler or repetition; each sentence carries distinct operational information.

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 three-parameter mutation tool with no output schema, the description covers the action, its destructive side effect, the clearing mechanism, the blocking precondition, and the natural follow-up call. An agent has enough to invoke it correctly without inspecting other tools.

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%, including the alias relationship between windowId and windowIds and the '[] or 0 removes all' semantics, so the schema already carries the parameter meaning. The description reinforces the multi-value and clearing behavior but adds no new syntax, format, or ordering detail beyond the schema.

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 and resource pair ('Bind ... accounts to ... closed NexBrowser windows') with scope (one or more of each) and a clear target object (closed windows). It is readily distinguishable from sibling nex_browser_bind_proxy, which binds proxies rather than catalog accounts.

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

Usage Guidelines5/5

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

Explicitly names the removal path (accountIds=[]), the precondition (windows must be closed; running windows are rejected), and the follow-up tool to use after opening (nex_browser_accounts). That is when-to-use, when-not-to-use, and the alternative in one compact block.

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