Skip to main content
Glama
nex-browser

NexBrowser MCP Server

Official
by nex-browser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

nex_browser_bind_proxy

Destructive

Assigns a proxy to one or more closed browser windows or removes it with proxyId 0, so you can route sessions through different proxies; close running windows before binding.

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.

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. Changed1 schema field changedv2026.10.24
    • changedInput schema / properties / windowIds / description
      Previous value: -"Documented alias of windowId"New value: +"Alias of windowId"
  2. 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"
+]
  3. Addedv2026.8.14

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true; the description goes substantially beyond that by explaining that binding overwrites an existing proxy binding, that running windows are rejected, and that no extra confirmation is needed when replacing a confirmed failed proxy. The explicit preservation advice (save task URL and form state before closing, reopen and verify the exit) is exactly the kind of irreversibility context annotations cannot express.

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

Conciseness4/5

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

Three sentences, front-loaded with the core action and the removal sentinel, then preconditions, then the risky-workflow note. Every sentence carries information, though the final clause ('reopen and verify the exit') is compressed enough to be slightly ambiguous.

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 3-parameter mutation tool with no output schema and only a destructiveHint annotation, the description covers preconditions, overwrite semantics, removal, and recovery workflow. It leaves partial-failure behavior and the shape of the bind result unstated, which is a minor gap rather than a blocking one.

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 all three parameters are already documented, including proxyId=0 removal and the windowId/windowIds alias relationship. The description adds only marginal semantics — the one-to-many cardinality of windows and the overwrite behavior of proxyId — so the baseline 3 applies.

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 — bind one proxy to one or more closed NexBrowser windows — and immediately covers the inverse operation (proxyId=0 removes the binding). The scope (closed windows only) is stated in the same breath, so an agent can distinguish it from nex_browser_bind_account or nex_browser_connect without opening a schema.

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 removal path (proxyId=0), plus workflow guidance for the failed-proxy replacement case. It does not name adjacent tools (e.g., nex_browser_close) that an agent would need to satisfy the closed-window requirement, so it stops short of full when/when-not/alternatives routing.

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