Skip to main content
Glama
uglyswap

internetbs-mcp

by uglyswap

domain_update

Update domain settings like nameservers, contacts, lock status, WHOIS privacy, and auto-renewal. Adjust configurations to keep domains accurate and secure.

Instructions

Update an existing domain's settings including nameservers, contacts, lock status, WHOIS privacy, and auto-renewal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain name to update (e.g. example.com)
ns_listNoComma-separated list of nameservers (e.g. ns1.example.com,ns2.example.com)
autoRenewNoEnable or disable auto-renewal
admin_emailNoAdmin contact email address
billing_emailNoBilling contact email address
admin_lastnameNoAdmin contact last name
admin_firstnameNoAdmin contact first name
registrant_cityNoRegistrant city
technical_emailNoTechnical contact email address
billing_lastnameNoBilling contact last name
registrant_emailNoRegistrant email address
billing_firstnameNoBilling contact first name
registrant_streetNoRegistrant street address
privateWhoisStatusNoSet WHOIS privacy level
technical_lastnameNoTechnical contact last name
registrant_lastnameNoRegistrant last name
registrarLockStatusNoSet registrar lock status to prevent unauthorized transfers
technical_firstnameNoTechnical contact first name
registrant_firstnameNoRegistrant first name
registrant_postalcodeNoRegistrant postal code
registrant_countrycodeNoRegistrant country code (e.g. US, FR, DE)
registrant_phonenumberNoRegistrant phone number (e.g. +1.5551234567)
registrant_organizationNoRegistrant organization
Behavior2/5

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

With no annotations, the description carries the full burden of disclosure. It indicates a mutation but fails to explain partial-update semantics (only supplied fields change), whether the domain must exist, or what the return value is. For a tool with 23 parameters, this is insufficient.

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, front-loaded sentence that states the action and scope efficiently without wasted words. It lists the key setting categories in a compact manner.

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?

Given the high parameter count (23), no annotations, and no output schema, this brief description is not complete. It omits how the update behaves (e.g., partial updates, reliance on domain existence) and how it relates to overlapping sibling tools, leaving agents underprepared.

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%, with each parameter already described. The description's list of categories (nameservers, contacts, lock, WHOIS, auto-renewal) adds no meaning beyond the schema, so the baseline of 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?

The description clearly states the tool updates existing domain settings and enumerates the main categories (nameservers, contacts, lock status, WHOIS privacy, auto-renewal). However, it does not explicitly differentiate from sibling tools like registrar_lock_enable/disable and private_whois_enable/disable, which overlap in functionality.

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 the dedicated registrar_lock_enable/disable or private_whois_enable/disable tools, nor any prerequisites or exclusions. The generic phrasing implies use for updating domain settings, but the overlap with specialized siblings remains unaddressed.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/uglyswap/internetbs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server