Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_bind_proxy

Destructive

Binds a proxy to one or more closed NexBrowser windows; proxyId=0 removes the binding. Close running windows first and save task URL/form state before replacing a failed proxy.

Instructions

Bind one proxy to one or more closed NexBrowser windows; proxyId=0 removes the binding. Running windows are rejected, so close them first. Replacing a confirmed failed proxy on the task window needs no extra confirmation: save the task URL and form state before closing, then reopen and verify the exit.

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": {
      "proxyId": "<proxyId>"
    },
    "name": "nex_browser_bind_proxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
proxyIdYesProxy resource ID to bind; 0 removes the proxy binding
windowIdNoOne window ID or a list of closed 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 / proxyId / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / proxyId / 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 closed window IDs"New value: +"One window ID or a list of closed 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",
      -  "proxyId"
      -]New value: +[
      +  "proxyId"
      +]
  4. Addedv2026.8.14

TDQS

A3.7/5.0
Behavior4/5

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

The destructiveHint annotation already marks this as mutating, and the description adds real context beyond it: running windows are rejected rather than auto-closed, and proxyId=0 is the unbind path. The closing sentence about replacing a failed proxy gives recovery guidance, though it is worded ambiguously and never defines 'the task window'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core binding/unbinding rule is front-loaded and efficient. The trailing sentence, however, packs three loosely connected workflow steps into one clause and references an undefined 'task window', making it hard to parse and only tangentially about invoking this tool.

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?

With three simple parameters, no output schema, and only a destructiveHint annotation, the description covers preconditions, the unbind path, and a recovery flow, which is close to sufficient. It leaves unclear whether a multi-window bind is atomic (all-or-nothing when one window is open) and what the call returns, which matters for a destructive operation.

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 proxyId=0, the windowId/windowIds aliasing, and the array form are all documented in the schema already. The description reinforces the 'closed windows only' constraint on window IDs, which is meaningful, but contributes no new syntax or format detail. 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 concrete verb and resource: binding a proxy to NexBrowser windows, with the special case that proxyId=0 removes the binding. An agent can distinguish this from nex_browser_bind_account and nex_proxy_modify without opening a schema, 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?

Gives a hard precondition ('Running windows are rejected, so close them first') and a sequencing note about saving task URL and form state before closing a window for proxy replacement. It stops short of naming alternatives (e.g. nex_proxy_modify for editing the proxy itself or nex_browser_bind_account for account binding), so the when-not case is only implied.

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