Skip to main content
Glama

Update proxy list

update_proxy_list
Idempotent

Updates an existing proxy list's name, geo targeting, rotation settings, or export format while keeping omitted fields and login unchanged; recreate the list to change its IP whitelist.

Instructions

Change an existing list's name, geo (country with region/city/isp/zip, or countries), rotation or format; omitted fields keep their values. The login stays the same. The IP whitelist (network) cannot be changed: delete the list and create a new one for that.

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": {
      "proxy_id": "<proxy_id>",
      "list_id": "<list_id>"
    },
    "name": "update_proxy_list"
  }
}

Input 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).
nameNo
formatNoSaved export-format preference for the dashboard. Does not change entries in the response. Each name lists the fields in order, ending in the separator (_colon, _comma, _at); login_pass_host_port is login:pass@host:port and the _url values add the scheme.
regionNoOnly valid with a single country (names from get_geo).
countryNoISO-3166-1 alpha-2, any case. Mutually exclusive with countries.
list_idYeslist_... id from get_proxy_status
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 fails
rotation_period_secondsNo0=new IP per request, -1=sticky, N=keep the IP for N seconds (max 86400)

Output Schema

NameRequiredDescriptionDefault
listYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / format / description
      Previous value: -"Saved export-format preference for the dashboard. Does not change entries in the response."New value: +"Saved export-format preference for the dashboard. Does not change entries in the response. Each name lists the fields in order, ending in the separator (_colon, _comma, _at); login_pass_host_port is login:pass@host:port and the _url values add the scheme."
    • changedInput schema / properties / format / enum
      Previous value: -[
      -  "login_pass_host_port",
      -  "host_port_login_pass",
      -  "http_url",
      -  "socks5_url",
      -  "host_port",
      -  "login_pass_at_host_port",
      -  "json"
      -]New value: +[
      +  "login_pass_host_port",
      +  "http_url",
      +  "socks5_url",
      +  "host_port_login_pass_colon",
      +  "login_pass_host_port_colon",
      +  "host_port_login_pass_comma",
      +  "login_pass_host_port_at"
      +]
    • changedInput schema / properties / list_id / description
      Previous value: -"list_... id from list_proxy_lists"New value: +"list_... id from get_proxy_status"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv1.2.1

TDQS

A4/5.0
Behavior3/5

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

With annotations declaring readOnlyHint=false, idempotentHint=true, destructiveHint=false, the bar is lower, and the description adds real context: omitted fields retain prior values (consistent with idempotency), the login is unchanged, and the network whitelist is immutable. It does not describe failure modes or what happens when country/countries conflict.

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 tight clauses: what changes, what stays the same, what cannot be changed. Front-loaded with the mutable fields and zero filler wording.

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 12-parameter partial-update mutation with an output schema and strong annotations, the description covers the critical gotchas (partial semantics, immutable whitelist, stable login). Minor gaps remain around conflicting geo inputs and preconditions for the proxy being active, which the schema partially covers.

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 coverage is 92%, so parameters are already well documented (the format enum even explains each serialization). The description restates the parameter groups in prose ('geo (country with region/city/isp/zip, or countries), rotation or format') and hints at the country-vs-countries exclusivity, but adds no syntax beyond the schema. Baseline 3 applies.

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 specific verb ('Change') and resource ('an existing list') and enumerates exactly which fields are updatable: name, geo, rotation, format. 'Existing list' plus the delete/create fallback for the whitelist distinguishes it clearly from create_proxy_list and delete_proxy_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?

Gives an explicit exclusion with an alternative: the IP whitelist cannot be updated — 'delete the list and create a new one for that.' Also clarifies partial-update behavior (omitted fields keep their values). No general guidance on checking the list via get_proxy_status first, though the schema mentions it for list_id.

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