Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_proxy_delete

Destructive

Deletes one or more custom proxy resources by ID, including single or bulk removal. Use it to clean up stored proxies when they are no longer needed.

Instructions

Delete one or more custom proxy resources. Bought channel proxies may be rejected by Desktop. Credentials are never returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nex_proxy_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoSingle-ID alias of proxyId
itemsNoAlias of proxyId
proxyIdNoOne proxy ID or a list of proxy IDs to delete
proxyIdsNoAlias of proxyId

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2026.11.3
    • removedInput schema / properties / id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / id / type
      Added value: +[
      +  "string",
      +  "number"
      +]
    • changedInput schema / properties / items / 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 / proxyId / 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 / proxyIds / 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 / items / description
      Previous value: -"Documented alias of proxyId"New value: +"Alias of proxyId"
  3. Addedv2026.8.20

TDQS

B3.2/5.0
Behavior3/5

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

Annotations supply only destructiveHint=true, so the description carries much of the burden. It adds one genuinely useful failure-mode hint (bought channel proxies may be rejected by Desktop) but omits the most important behavior for a delete: irreversibility, whether deletion cascades to browsers bound to the proxy, and what the response contains. The 'credentials are never returned' sentence is a weak substitute for real return-value disclosure.

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 short sentences with the action front-loaded; nothing is padded or redundant in structure. The closing sentence about credentials is only loosely relevant to a delete operation and marginally dilutes focus, keeping it below a 5.

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?

For a destructive, multi-ID mutation with no output schema and minimal annotations, an agent still lacks irreversibility status, side effects on bound browsers, and partial-failure semantics when deleting a list. The description covers what it deletes and one rejection case, but not enough for confident invocation in an automated flow.

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%, and every one of the four parameters is self-described as an ID or alias of proxyId, so the schema already does the work. The description adds only the 'one or more' plurality hint, which is consistent with the anyOf string/array shape but adds no alias-resolution or ID-format detail.

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?

The description gives a specific verb and resource ('Delete one or more custom proxy resources') and signals batch capability via 'one or more'. It does not name or contrast with siblings such as nex_proxy_modify or nex_proxy_list, but the operation itself is unambiguous.

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

Usage Guidelines2/5

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

There is no explicit when-to-use/when-not-to-use guidance and no pointer to alternatives (e.g., nex_proxy_modify for edits, nex_proxy_list for inspection). The clause 'Bought channel proxies may be rejected by Desktop' implies a scope restriction — only custom proxies are deletable — but it is phrased so vaguely that an agent cannot tell whether it describes a hard precondition, an error case, or a UI quirk.

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