Skip to main content
Glama

Create proxy list

create_proxy_list

Create geo-targeted proxy lists on a shared proxy: pick one country with optional region, city, ISP or ZIP, or 2-30 countries, and get ready-to-paste http:// or socks5:// URLs.

Instructions

Create a geo-targeted list on an active shared proxy (up to 100 lists, all sharing the proxy's data). Provide either a single country (optional region/city/isp/zip, see get_geo) or a countries array (2-30, no subfilters). By default it gets its own login and returns ready-to-paste http:// and socks5:// URLs (entries are login:pass@host:port). With network, it authenticates by source IP instead (no login; set at creation only). Change geo, rotation or format later with update_proxy_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ispNoOnly valid with a single country (names from get_geo).
zipNoOnly valid with a single country.
cityNoOnly valid with a single country (names from get_geo).
nameYes
formatNoSaved export-format preference for the dashboard. Does not change entries in the response.login_pass_host_port
regionNoOnly valid with a single country (names from get_geo).
countryNoISO-3166-1 alpha-2, any case. Mutually exclusive with countries.
networkNoIP whitelist instead of a login: comma-separated IPv4 addresses and/or /24-/32 subnets, max 5 (e.g. '203.0.113.7,198.51.100.0/24'). Cannot be changed later; an address can be on one list at a time.
proxy_idYesprx_... id of an active shared proxy
countriesNo2-30 ISO-3166-1 alpha-2 codes. Mutually exclusive with country/subfilters.
rotation_modeNoWhat happens when the current node failsinstant
rotation_period_secondsNo0=new IP per request, -1=sticky, N=keep the IP for N seconds (max 86400)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
listYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.2.1
    • changedInput schema / properties / city / description
      Previous value: -"Only valid with a single country."New value: +"Only valid with a single country (names from get_geo)."
    • addedInput schema / properties / city / maxLength
      Added value: +80
    • addedInput schema / properties / countries / items / pattern
      Added value: +"^[A-Za-z]{2}$"
    • addedInput schema / properties / countries / maxItems
      Added value: +30
    • addedInput schema / properties / countries / minItems
      Added value: +2
    • addedInput schema / properties / country / pattern
      Added value: +"^[A-Za-z]{2}$"
    • changedInput schema / properties / isp / description
      Previous value: -"Only valid with a single country."New value: +"Only valid with a single country (names from get_geo)."
    • addedInput schema / properties / isp / maxLength
      Added value: +80
    • addedInput schema / properties / network
      Added value: +{
      +  "description": "IP whitelist instead of a login: comma-separated IPv4 addresses and/or /24-/32 subnets, max 5 (e.g. '203.0.113.7,198.51.100.0/24'). Cannot be changed later; an address can be on one list at a time.",
      +  "maxLength": 120,
      +  "type": "string"
      +}
    • changedInput schema / properties / region / description
      Previous value: -"Only valid with a single country."New value: +"Only valid with a single country (names from get_geo)."
    • addedInput schema / properties / region / maxLength
      Added value: +80
    • addedInput schema / properties / zip / maxLength
      Added value: +20
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "list": {
      +      "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"
      +    }
      +  },
      +  "required": [
      +    "list"
      +  ],
      +  "type": "object"
      +}
  2. Changed11 schema fields changedv1.1.8
    • changedInput schema / properties / country / description
      Previous value: -"ISO-3166-1 alpha-2, lowercased. Mutually exclusive with countries."New value: +"ISO-3166-1 alpha-2, any case. Mutually exclusive with countries."
    • changedInput schema / properties / format / description
      Previous value: -"Output format for entries[] (e.g. login_pass_host_port, http_url, socks5_url)"New value: +"Saved export-format preference for the dashboard. Does not change entries in the response."
    • addedInput schema / properties / format / enum
      Added value: +[
      +  "login_pass_host_port",
      +  "host_port_login_pass",
      +  "http_url",
      +  "socks5_url",
      +  "host_port",
      +  "login_pass_at_host_port",
      +  "json"
      +]
    • addedInput schema / properties / name / maxLength
      Added value: +60
    • addedInput schema / properties / name / minLength
      Added value: +1
    • addedInput schema / properties / proxy_id / description
      Added value: +"prx_... id of an active shared proxy"
    • addedInput schema / properties / proxy_id / pattern
      Added value: +"^(?:prx_[A-Za-z0-9_-]{1,64}|PRX[A-Za-z0-9]{1,32})$"
    • addedInput schema / properties / rotation_mode / description
      Added value: +"What happens when the current node fails"
    • changedInput schema / properties / rotation_period_seconds / description
      Previous value: -"0=per-request, -1=sticky, N=seconds (max 86400)"New value: +"0=new IP per request, -1=sticky, N=keep the IP for N seconds (max 86400)"
    • changedInput schema / properties / rotation_period_seconds / maximum
      Previous value: -9007199254740991New value: +86400
    • changedInput schema / properties / rotation_period_seconds / minimum
      Previous value: --9007199254740991New value: +-1
  3. First observedv1.1.3

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare mutation/safety hints, and the description adds substantive context beyond them: a 100-list cap sharing the proxy's data, the default per-list login vs the source-IP 'network' auth mode, that network is set at creation only and cannot be changed, and that an address can be on only one list at a time. These are non-obvious constraints that materially affect invocation.

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?

Roughly four dense sentences but front-loaded with the core action, then the mode choice, then output/auth behavior, then the follow-up tool. Every clause carries information; only the URL-format parenthetical ('entries are login:pass@host:port') is mildly redundant with the format enum.

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?

For a 12-parameter create tool with an output schema and mostly-covered params, the description covers prerequisites (active shared proxy), the two mutually exclusive geo modes, auth mode, and follow-up mutation path. Nothing needed to call it correctly is missing, and return values are covered by the output schema.

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 coverage is 92% so the baseline is 3, but the description adds cross-parameter meaning the schema states only locally: country/countries mutual exclusivity, subfilters being valid only with a single country, and the default-login behavior tied to the network parameter. It largely mirrors the schema's per-field notes rather than adding new syntax detail, so it stops short of 5.

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 precise verb+resource+scope: 'Create a geo-targeted list on an active shared proxy'. The 'on an active shared proxy' qualifier separates it from purchase_proxy, and the list-management siblings (list/update/delete_proxy_list) are clearly differentiated by the creation verb.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use get_geo for names, use update_proxy_list to change geo/rotation/format later. It also states the selection condition between the two geo modes (single country with optional subfilters vs a 2-30 countries array with no subfilters), which is exactly the decision an agent must make.

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