Skip to main content
Glama

Activate Affiliate

whmcs_activate_affiliate

Activate a client as an affiliate by providing their client ID to enable affiliate tracking and commissions.

Instructions

Activate a client as an affiliate

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useridYesClient ID

Implementation Reference

  • src/index.ts:1183-1198 (registration)
    Registration of the 'whmcs_activate_affiliate' tool with MCP server, defining its input schema (userid) and delegating to whmcsClient.affiliateActivate()
    server.registerTool(
        'whmcs_activate_affiliate',
        {
            title: 'Activate Affiliate',
            description: 'Activate a client as an affiliate',
            inputSchema: {
                userid: z.number().describe('Client ID'),
            },
        },
        async (params) => {
            const result = await whmcsClient.affiliateActivate(params);
            return {
                content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
            };
        }
    );
  • Handler function that calls the WHMCS 'AffiliateActivate' API action with the provided userid parameter, returning an affiliateid upon success
    async affiliateActivate(params: { userid: number }) {
        return this.call<WhmcsApiResponse & { affiliateid: number }>('AffiliateActivate', params);
    }
  • Input validation schema for the tool - requires a single 'userid' (number) field representing the client ID to activate as an affiliate
        inputSchema: {
            userid: z.number().describe('Client ID'),
        },
    },
  • Generic API request helper used by affiliateActivate to call the WHMCS API with authentication and error handling
    async call<T extends WhmcsApiResponse>(action: string, params: Record<string, unknown> = {}): Promise<T> {
        const url = `${this.config.apiUrl.replace(/\/$/, '')}/includes/api.php`;
        
        const postData: Record<string, string> = {
            identifier: this.config.apiIdentifier,
            secret: this.config.apiSecret,
            action: action,
            responsetype: 'json',
            ...this.flattenParams(params)
        };
    
        if (this.config.accessKey) {
            postData.accesskey = this.config.accessKey;
        }
    
        const response = await fetch(url, {
            method: 'POST',
            headers: {
                'Content-Type': 'application/x-www-form-urlencoded',
            },
            body: new URLSearchParams(postData).toString(),
        });
    
        if (!response.ok) {
            throw new Error(`WHMCS API request failed: ${response.status} ${response.statusText}`);
        }
    
        const data = await response.json() as T;
        
        if (data.result === 'error') {
            throw new Error(`WHMCS API error: ${data.message || 'Unknown error'}`);
        }
    
        return data;
    }
Behavior2/5

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

No annotations provided, and the description does not disclose side effects, permissions, or what the activation entails (e.g., record creation, email notification). The description adds minimal behavioral context.

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

Conciseness4/5

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

The description is a single sentence, front-loaded, and wastes no words. However, it could be slightly more informative without being verbose.

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

Completeness3/5

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

For a simple tool with one parameter and no output schema, the description is minimal but adequate. It lacks details on return values, error conditions, or the effect of activation.

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% (one parameter 'userid' described as 'Client ID'). The description adds no extra meaning beyond the schema, resulting in a baseline score.

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 'Activate a client as an affiliate' clearly states the verb (activate) and resource (client as affiliate), distinguishing it from siblings like 'add_client' or 'get_affiliates'.

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, such as prerequisites for a client to be eligible, or contrast with related tools like 'add_client' or 'get_affiliates'.

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