Skip to main content
Glama
Yadley

WHMCS MCP Server

by Yadley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update Client

whmcs_update_client

Updates an existing client's profile in WHMCS, including contact details, status, credit balance, and password.

Instructions

Update an existing client in WHMCS

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity
emailNoClient email address
notesNoAdmin notes
stateNoState/Province
creditNoCredit balance
statusNoClient status (Active, Inactive, Closed)
countryNoCountry (2-letter ISO code)
address1NoStreet address
address2NoAddress line 2
clientidYesThe client ID to update
languageNoClient language
lastnameNoClient last name
postcodeNoPostal/ZIP code
firstnameNoClient first name
password2NoNew password
companynameNoCompany name
phonenumberNoPhone number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

C2.6/5.0
Behavior1/5

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

With no annotations, the description carries full burden but only says 'Update an existing client', failing to disclose data mutation, field merge behavior, error handling, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is too brief; it merely restates the tool name without providing useful context or justification for its conciseness.

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

Completeness1/5

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

For a mutation tool with 17 parameters and no output schema, the description fails to explain expected output, side effects, or typical use cases, leaving the agent underinformed.

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 100%, so baseline is 3. Description adds no extra meaning beyond parameter descriptions already in schema.

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?

Clearly states the verb 'Update' and resource 'existing client' in WHMCS, distinctly differentiating from sibling tools like whmcs_add_client and whmcs_delete_client.

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 on when to use this tool versus alternatives, no mention of prerequisites (e.g., client must exist), and no exclusions or contexts provided.

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