whmcs_get_client_domainsRetrieve all domains owned by a client in WHMCS. Use filters like client ID or domain name to locate specific domain records for account management, troubleshooting, or reporting.
Get domains owned by a client
| Name | Required | Description | Default |
|---|---|---|---|
| domain | No | Filter by domain name | |
| clientid | No | The client ID | |
| domainid | No | Specific domain ID | |
| limitnum | No | Number of results | |
| limitstart | No | Starting offset |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full behavioral disclosure burden. It fails to mention any side effects, permissions, return format, or pagination behavior. Simply 'Get domains' 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with no wasted words. However, given the lack of annotations and multiple parameters, additional context would be beneficial without harming conciseness.
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?
No output schema exists, so description should explain what is returned (e.g., list of domain objects). It does not. Also missing behavioral context for a 5-param tool with optional filters.
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?
Schema coverage is 100% as all 5 parameters have descriptions. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.
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?
The description 'Get domains owned by a client' clearly states the verb (get) and resource (domains). It differentiates from sibling tools like whmcs_get_client_products by focusing on domains, but it does not elaborate on scope or filtering.
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 provided on when to use this tool versus alternatives (e.g., whmcs_get_domain_lock_status). No exclusions or context for optimal use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.