Skip to main content
Glama

Delete Client

whmcs_delete_client

Permanently delete a client from WHMCS using the client ID. Use this tool with caution as the removal cannot be undone.

Instructions

Delete a client from WHMCS (use with caution)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientidYesThe client ID to delete

Implementation Reference

  • The handler method `deleteClient` in `WhmcsApiClient` class that executes the actual API call to delete a client via WHMCS API action 'DeleteClient'.
    async deleteClient(params: { clientid: number }) {
        return this.call<WhmcsApiResponse>('DeleteClient', params);
    }
  • Input schema definition for the 'whmcs_delete_client' tool: requires a `clientid` (number) parameter describing the client ID to delete.
        clientid: z.number().describe('The client ID to delete'),
    },
  • src/index.ts:156-171 (registration)
    Registration of the 'whmcs_delete_client' tool via `server.registerTool()` with title 'Delete Client', description, input schema, and the async handler that delegates to `whmcsClient.deleteClient(params)`.
    server.registerTool(
        'whmcs_delete_client',
        {
            title: 'Delete Client',
            description: 'Delete a client from WHMCS (use with caution)',
            inputSchema: {
                clientid: z.number().describe('The client ID to delete'),
            },
        },
        async (params) => {
            const result = await whmcsClient.deleteClient(params);
            return {
                content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
            };
        }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action is destructive via 'use with caution', but fails to disclose consequences like irreversibility, cascading effects on orders/invoices, or required admin privileges.

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 with no extraneous words. It efficiently conveys the core purpose and a warning.

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 destructive tool with no output schema and no annotations, the description is too sparse. It should explain what happens to associated data (e.g., orders, invoices) whether the action is reversible, and any permission requirements.

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%, and the parameter 'clientid' is described in the schema. The description adds no additional meaning beyond what the schema already provides, so it meets the baseline.

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?

The description 'Delete a client from WHMCS' clearly states the action (delete) and the resource (client), distinguishing it from sibling tools like add, update, or get client operations.

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?

The only guideline is 'use with caution', which is vague. No explicit when-to-use, when-not-to-use, or alternatives are provided. An agent would not know if deletion requires specific permissions or has prerequisites.

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/scarecr0w12/whmcs-mcp-tool'

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