Skip to main content
Glama
Sign In
GoLogin MCP

GoLogin MCP

Official
by gologinapp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

post_users_proxies_mobile_proxy

Generate high-quality mobile proxies with specific country codes, cities, and customizable names. Link proxies to profiles for efficient management and automation in GoLogin.

Instructions

Create gologin high quality proxy

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": {
      "countryCode": "<countryCode>"
    },
    "name": "post_users_proxies_mobile_proxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoif you want a proxy in a specific city you can specify it here.
countryCodeYesCountry cod with 2 lowercase letters
customNameNoCustom name for proxy for proxy management.
isDCNoIs DC means that you want to get a datacenter proxy.
isMobileNoGologin has 3 type of proxies: mobile, datacenter and residential. This parameter means that you want to get a mobile proxy.
profileIdToLinkNoPut here profile id if you want to add this proxy to profiles after creation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Create' but doesn't specify whether this is a write operation, what permissions are needed, if it's idempotent, or what happens on failure. This leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it highly concise and well-structured for quick comprehension.

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

Completeness2/5

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

For a creation tool with 6 parameters, no annotations, and no output schema, the description is inadequate. It lacks details on behavioral traits, usage context, and expected outcomes, making it incomplete for effective agent use despite the concise phrasing.

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%, so the schema fully documents all 6 parameters. The description adds no additional parameter information beyond what's in the schema, resulting in a baseline score of 3 as it doesn't compensate but also doesn't detract.

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 clearly states the action ('Create') and resource ('gologin high quality proxy'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'post_proxy_add_proxies' or 'post_proxy_delete_proxies', which prevents a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives like 'post_proxy_add_proxies' or other proxy-related tools. The description lacks context about prerequisites, timing, or exclusions, offering minimal usage direction.

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

Related Tools