VoidMob MCP

Official

by voidmobcom

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List proxy lists

list_proxy_lists

Read-onlyIdempotent

List sub-pools for a given shared proxy to view each geo-targeted list's login or IP whitelist and rotation settings.

Instructions

List the proxy lists on a shared proxy: geo-targeted sub-pools, each with its own login (or IP whitelist) and rotation settings, all sharing the proxy's data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`proxy_id`	Yes	prx_... id of a shared proxy

Output Schema

TableJSON Schema

Name	Required	Description	Default
`lists`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.1Oct 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "lists": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "activation_note": {
+            "type": "string"
+          },
+          "city": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "countries": {
+            "anyOf": [
+              {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "country": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "credentials": {
+            "anyOf": [
+              {
+                "additionalProperties": {},
+                "properties": {
+                  "host": {
+                    "type": "string"
+                  },
+                  "password": {
+                    "type": "string"
+                  },
+                  "port": {
+                    "maximum": 9007199254740991,
+                    "minimum": -9007199254740991,
+                    "type": "integer"
+                  },
+                  "protocol": {
+                    "type": "string"
+                  },
+                  "username": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "host",
+                  "port",
+                  "protocol",
+                  "username",
+                  "password"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "entries": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "format": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "isp": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "network": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "proxy_id": {
+            "type": "string"
+          },
+          "region": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "rotation_mode": {
+            "type": "string"
+          },
+          "rotation_period_seconds": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "zip": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "proxy_id",
+          "name",
+          "rotation_period_seconds",
+          "rotation_mode",
+          "format",
+          "credentials",
+          "entries",
+          "activation_note",
+          "created_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "lists"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv1.1.8Sep 30, 2026
- addedInput schema / properties / proxy_id / description
```
Added value: +"prx_... id of a shared proxy"
```
- addedInput schema / properties / proxy_id / pattern
```
Added value: +"^(?:prx_[A-Za-z0-9_-]{1,64}|PRX[A-Za-z0-9]{1,32})$"
```
First observedv1.1.3Aug 11, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds domain context (what constitutes a proxy list) but discloses nothing about pagination, result size, or auth requirements beyond what annotations provide, so it earns a middling score against the lowered annotation bar.

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?

One compact sentence with the action front-loaded. It is efficient, though a share of the sentence is spent defining the domain object rather than the tool's behavior.

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?

With a rich output schema and full annotation coverage, the description needn't explain return values or safety. The remaining omission is pagination/result-set behavior for a list operation, which is minor given how much structured data accompanies the tool.

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 the single proxy_id parameter is fully documented in the schema (pattern and 'prx_... id of a shared proxy'). The description says nothing about the parameter, so it adds no meaning beyond the schema — 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 ('List the proxy lists') and immediately defines what a proxy list is (geo-targeted sub-pools with own login/whitelist and rotation settings). This clearly separates it from create_proxy_list/update_proxy_list/delete_proxy_list by implication, but it never names those siblings explicitly, so it falls short of a 5.

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?

The scope 'on a shared proxy' hints at the precondition, but there is no explicit when-to-use, when-not-to-use, or reference to which sibling to choose instead. For a family that includes create/update/delete_proxy_list, the absence of routing guidance is a real gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.