Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

billing_enableAutoRenewalV1

Enable auto-renewal for a subscription to prevent service interruption. Provide the subscription ID to activate automatic renewal.

Instructions

Enable auto-renewal for a subscription.

Use this endpoint when enable auto-renewal for a subscription.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriptionIdYesSubscription ID

Implementation Reference

  • Tool definition/schema for billing_enableAutoRenewalV1. Defines the tool name, description, method (PATCH), path (/api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/enable), and input schema requiring subscriptionId.
    {
      "name": "billing_enableAutoRenewalV1",
      "description": "Enable auto-renewal for a subscription.\n\nUse this endpoint when enable auto-renewal for a subscription.",
      "method": "PATCH",
      "path": "/api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/enable",
      "inputSchema": {
        "type": "object",
        "properties": {
          "subscriptionId": {
            "type": "string",
            "description": "Subscription ID"
          }
        },
        "required": [
          "subscriptionId"
        ]
      },
      "security": [
        {
          "apiToken": []
        }
      ],
      "group": "billing"
    }
  • TypeScript type definition/schema for billing_enableAutoRenewalV1. Same as JS version but exported as part of typed OpenApiTool array.
    {
      "name": "billing_enableAutoRenewalV1",
      "description": "Enable auto-renewal for a subscription.\n\nUse this endpoint when enable auto-renewal for a subscription.",
      "method": "PATCH",
      "path": "/api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/enable",
      "inputSchema": {
        "type": "object",
        "properties": {
          "subscriptionId": {
            "type": "string",
            "description": "Subscription ID"
          }
        },
        "required": [
          "subscriptionId"
        ]
      },
      "security": [
        {
          "apiToken": []
        }
      ],
      "group": "billing"
    }
  • Server entry point that registers all billing tools (including billing_enableAutoRenewalV1) by importing the tools array and passing to startServer.
    #!/usr/bin/env node
    // Auto-generated entry for group: billing
    import { startServer } from '../core/runtime.js';
    import tools from '../core/tools/billing.js';
    
    startServer({ name: 'hostinger-billing-mcp', version: '0.1.40', tools });
  • Generic API call handler (executeApiCall) that handles billing_enableAutoRenewalV1. Since this tool is not marked as 'custom', it's executed as a standard API call: it extracts subscriptionId from params, substitutes it into the path PATCH /api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/enable, and sends the HTTP request.
    async executeApiCall(tool, params) {
      // Get method and path from tool
      const method = tool.method;
      let path = tool.path;
    
      // Clone params to avoid modifying the original
      const requestParams = { ...params };
    
      // Replace path parameters with values from params
      Object.entries(requestParams).forEach(([key, value]) => {
        const placeholder = `{${key}}`;
        if (path.includes(placeholder)) {
          path = path.replace(placeholder, encodeURIComponent(String(value)));
          delete requestParams[key]; // Remove used parameter
        }
      });
    
      // Build the full URL
      const baseUrl = this.baseUrl.endsWith("/") ? this.baseUrl : `${this.baseUrl}/`;
      const cleanPath = path.startsWith("/") ? path.slice(1) : path;
      const url = new URL(cleanPath, baseUrl).toString();
    
      this.log('debug', `API Request: ${method} ${url}`);
    
      try {
        // Configure the request
        const config = {
          method: method.toLowerCase(),
          url,
          headers: { ...this.headers },
          timeout: 60000, // 60s
          validateStatus: function (status) {
            return status < 500; // Resolve only if the status code is less than 500
          }
        };
      
        const bearerToken = process.env['API_TOKEN'] || process.env['APITOKEN']; // APITOKEN for backwards compatibility
        if (bearerToken) {
          config.headers['Authorization'] = `Bearer ${bearerToken}`;
        } else {
          this.log('error', `Bearer Token environment variable not found: API_TOKEN`);
        }
    
        // Add parameters based on request method
        if (["GET", "DELETE"].includes(method)) {
          // For GET/DELETE, send params as query string
          config.params = { ...(config.params || {}), ...requestParams };
        } else {
          // For POST/PUT/PATCH, send params as JSON body
          config.data = requestParams;
          config.headers["Content-Type"] = "application/json";
        }
    
        this.log('debug', "Request config:", {
          url: config.url,
          method: config.method,
          params: config.params,
          headers: Object.keys(config.headers)
        });
    
        // Execute the request
        const response = await axios(config);
        this.log('debug', `Response status: ${response.status}`);
    
        return response.data;
    
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        this.log('error', `API request failed: ${errorMessage}`);
    
        if (axios.isAxiosError(error)) {
          const responseData = error.response?.data;
          const responseStatus = error.response?.status;
    
          this.log('error', 'API Error Details:', {
            status: responseStatus,
            data: typeof responseData === 'object' ? JSON.stringify(responseData) : responseData
          });
    
          // Rethrow with more context for better error handling
          const detailedError = new Error(`API request failed with status ${responseStatus}: ${errorMessage}`);
          detailedError.response = error.response;
          throw detailedError;
        }
    
        throw error;
      }
    }
    
    /**
     * Log messages with appropriate level
     * Only sends to MCP if we're connected
     */
    log(level, message, data) {
      // Always log to stderr for visibility
      console.error(`[${level.toUpperCase()}] ${message}${data ? ': ' + JSON.stringify(data) : ''}`);
    
      // Only try to send via MCP if we're in debug mode or it's important
      if (this.debug || level !== 'debug') {
        try {
          // Only send if server exists and is connected
          if (this.server && this.server.isConnected) {
            this.server.sendLoggingMessage({
              level,
              data: `[MCP Server] ${message}${data ? ': ' + JSON.stringify(data) : ''}`
            });
          }
        } catch (e) {
          // If logging fails, log to stderr
          console.error('Failed to send log via MCP:', e.message);
        }
      }
    }
    
    /**
     * Create and configure Express app with shared middleware
     */
    createApp() {
      const app = express();
      app.use(express.json());
      app.use(cors());
Behavior2/5

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

No annotations provided, and the description only says it 'enables auto-renewal' without mentioning side effects, permissions, idempotency, or what happens to the subscription state. Lacks behavioral detail for a mutation tool.

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

Conciseness3/5

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

The description is short but contains a redundant sentence. Could be condensed to one clear sentence without loss of information.

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?

Given the complexity of billing operations and the presence of sibling tools for disabling auto-renewal, the description is too minimal. It doesn't define what auto-renewal means, prerequisites, or response format.

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 schema already describes 'subscriptionId' as 'Subscription ID'. The description adds no additional meaning beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it enables auto-renewal for a subscription, and it's distinguishable from the sibling billing_disableAutoRenewalV1. However, the second sentence is redundant and grammatically awkward.

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 explicit guidance on when to use or alternatives. The only hint is the tautological 'use this endpoint when enable auto-renewal', which offers no real context.

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/hostinger/api-mcp-server'

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