Skip to main content
Glama
mobileproxy

@mobileproxy/mcp-server

Official
by mobileproxy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List my proxies

list_proxies
Read-only

Retrieve and filter all proxies owned by the authenticated user, returning connection details, proxy IDs, and geo/operator data. Filter by type or country and hide expired proxies.

Instructions

Returns all proxies owned by the authenticated user with full connection details (host, port, login, password, geo, operator, expiration), and the proxy_id values other tools take. Supports filtering by type (mobile/server/backconnect/residential) and by country (ISO code or numeric id_country). Backconnect and residential proxies carry no country id, so a country filter excludes them. The server already drops expired proxies, but active_only rechecks client-side as a safety net.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by proxy type
countryNoFilter by 2-letter ISO country code (RU, US, TR, ...)
id_countryNoFilter by numeric country ID; takes precedence over country
active_onlyNoHide expired proxies (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Filter by 2-letter ISO country code (RU, US, TR, ...)",
+  "maxLength": 2,
+  "minLength": 2,
+  "type": "string"
+}
    • changedInput schema / properties / id_country / description
      Previous value: -"Filter by numeric country ID (not ISO code)"New value: +"Filter by numeric country ID; takes precedence over country"
  2. First observedv0.1.2

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the readOnlyHint and openWorldHint annotations: it discloses that sensitive connection details including login and password are returned, explains how filtering affects backconnect/residential proxies, and clarifies that the server already drops expired proxies while active_only rechecks client-side.

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?

The description is compact and front-loaded: it first states what is returned, then filters, then the key caveats. Every sentence contributes either output detail, filtering behavior, or an important semantic constraint, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description appropriately summarizes the return fields and the proxy_id usefulness. Combined with annotations that already declare it a safe read operation, the definition is complete enough for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is already 100%, so the baseline is 3. The description adds useful meaning by enumerating the type values, explaining country as ISO code or numeric id_country, and noting that backconnect/residential proxies lack a country id and will be excluded by country filtering.

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?

The description uses a specific verb and resource: it returns all proxies owned by the authenticated user, and it states the returned fields (host, port, login, password, geo, operator, expiration) plus the proxy_id values other tools consume. This clearly distinguishes it from sibling tools such as get_proxy_status or get_geo_list.

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?

The description gives clear context for using the tool, including supported filters and the important caveat that backconnect and residential proxies have no country id and are therefore excluded by a country filter. It does not explicitly name alternative siblings for specific sub-cases, but the intended usage is unambiguous.

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