whmcs_update_domain_nameserversSet new nameservers for a domain by providing domain ID and up to five nameservers. Changes DNS settings in WHMCS.
Update nameservers for a domain
| Name | Required | Description | Default |
|---|---|---|---|
| ns1 | No | Nameserver 1 | |
| ns2 | No | Nameserver 2 | |
| ns3 | No | Nameserver 3 | |
| ns4 | No | Nameserver 4 | |
| ns5 | No | Nameserver 5 | |
| domainid | Yes | Domain ID |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description fails to disclose behavioral traits such as authentication requirements, validation steps, or whether the operation is destructive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise single sentence, but lacks necessary detail; still not verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 6 parameters and no annotations or output schema, the description is insufficiently complete to guide proper usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema fully describes parameters, so description adds minimal value; baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Describes the specific action (update nameservers) and resource (domain), but does not differentiate from sibling tools like get_domain_nameservers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like get_domain_nameservers or other domain update tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.