Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_proxy_batch_create

Create multiple custom proxy resources at once from an items array, each requiring host and port. Supports SOCKS5, HTTP, or HTTPS with optional credentials that are never returned.

Instructions

Create multiple custom proxy resources from an items array. Each item needs host and port. Credentials are never returned.

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": {
      "items": "<items>"
    },
    "name": "nex_proxy_batch_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesProxy objects; each item needs host and port. Also accepts proxies or proxyList

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2026.11.3
    • removedInput schema / properties / items / items / properties / port / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / items / items / properties / port / type
      Added value: +[
      +  "string",
      +  "number"
      +]
  2. Changed3 schema fields changedv2026.10.24
    • changedInput schema / properties / items / items / properties / password / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
    • changedInput schema / properties / items / items / properties / protocol / description
      Previous value: -"SOCKS5, HTTP, or HTTPS; omitted create defaults to SOCKS5"New value: +"SOCKS5, HTTP or HTTPS; defaults to SOCKS5 when creating"
    • changedInput schema / properties / items / items / properties / username / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
  3. Addedv2026.8.20

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that credentials are write-only and never returned, and that creation is a mutation. It says nothing about required auth/permissions, batch size limits, or what happens when some items fail (partial success vs atomic rollback), which matters for a batch mutation.

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, zero waste, with the core action stated first and the per-item requirement immediately after. Nothing is buried or repeated.

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 single-parameter batch mutation with no annotations or output schema, the description covers what the tool does, the minimum item shape, and a key output-related fact (credentials hidden). The main gap is failure semantics for partial batches, which a caller would reasonably want to know.

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 host, port, protocol, ipVersion, username and password are already documented. The description only restates the host/port requirement and adds the credentials-never-returned note, which is about output rather than input semantics. 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: 'Create multiple custom proxy resources from an items array.' The word 'multiple' signals this is the batch counterpart to the singular nex_proxy_create, though the sibling is not 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 Guidelines3/5

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

Batch usage is implied by 'multiple' and 'items array', so an agent can infer this is for creating several proxies at once rather than one. However, there is no explicit when-to-use or when-not-to-use guidance and no reference to the alternative single-create 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