Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

VPS_updatePostInstallScriptV1

Modify an existing automation script by providing its ID, a new name, and updated content. Useful for adjusting VPS post-install behavior.

Instructions

Update a specific post-install script.

Use this endpoint to modify existing automation scripts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
postInstallScriptIdYesPost-install script ID
nameYesName of the script
contentYesContent of the script

Implementation Reference

  • Schema/definition of the VPS_updatePostInstallScriptV1 tool: a PUT request to /api/vps/v1/post-install-scripts/{postInstallScriptId} with input properties for postInstallScriptId (integer), name (string), and content (string), all required.
    {
      "name": "VPS_updatePostInstallScriptV1",
      "description": "Update a specific post-install script.\n\nUse this endpoint to modify existing automation scripts.",
      "method": "PUT",
      "path": "/api/vps/v1/post-install-scripts/{postInstallScriptId}",
      "inputSchema": {
        "type": "object",
        "properties": {
          "postInstallScriptId": {
            "type": "integer",
            "description": "Post-install script ID"
          },
          "name": {
            "type": "string",
            "description": "Name of the script"
          },
          "content": {
            "type": "string",
            "description": "Content of the script"
          }
        },
        "required": [
          "postInstallScriptId",
          "name",
          "content"
        ]
      },
      "security": [
        {
          "apiToken": []
        }
      ],
      "group": "vps"
  • src/servers/vps.ts:3-6 (registration)
    Registration entry point: imports the tools array from src/core/tools/vps.ts and passes it to startServer, which registers all tools including VPS_updatePostInstallScriptV1 with the MCP server.
    import { startServer } from '../core/runtime.js';
    import tools from '../core/tools/vps.js';
    
    startServer({ name: 'hostinger-vps-mcp', version: '0.1.42', tools });
  • Handler/execution logic for the tool. Since VPS_updatePostInstallScriptV1 is an API-based tool (not custom), the executeApiCall method in MCPServer (runtime.ts) handles it: it takes the tool's method (PUT) and path, substitutes path parameters (postInstallScriptId), sends the remaining params (name, content) as JSON body in a PUT request via axios.
    private async executeApiCall(tool: OpenApiTool, params: Record<string, any>): Promise<any> {
      // 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: AxiosRequestConfig = {
          method: method.toLowerCase(),
          url,
          headers: { ...this.headers },
          timeout: 60000, // 60s
          validateStatus: function (status: number): boolean {
            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) {
          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;
          if (config.headers) {
            config.headers["Content-Type"] = "application/json";
          }
        }
    
        this.log('debug', "Request config:", {
          url: config.url,
          method: config.method,
          params: config.params,
          headers: config.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 axiosError = error as AxiosError;
          const responseData = axiosError.response?.data;
          const responseStatus = axiosError.response?.status;
    
          this.log('error', 'API Error Details:', {
            status: responseStatus,
            data: typeof responseData === 'object' ? JSON.stringify(responseData) : String(responseData)
          });
    
          // Rethrow with more context for better error handling
          const detailedError = new Error(`API request failed with status ${responseStatus}: ${errorMessage}`);
          (detailedError as any).response = axiosError.response;
          throw detailedError;
        }
    
        throw error;
      }
    }
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the action (update/modify) without discussing side effects, permissions, reversibility, or what happens to the previous script. This is insufficient 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.

Conciseness5/5

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

The description is extremely concise with two sentences, no filler, and front-loads the core action. Every sentence earns its place.

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?

The description lacks crucial context for a modification tool: no mention of return value, success indicators, or prerequisite that the script ID must exist. Given no output schema, the description should compensate but does not.

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 description coverage is 100%, so each parameter already has a description. The tool description adds no extra meaning beyond what the schema provides, warranting the baseline score of 3.

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 clearly states the verb 'Update' and the resource 'post-install script', and explicitly says 'modify existing automation scripts'. This distinctly separates it from sibling tools like create and delete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use (modify existing scripts) but does not explicitly exclude other cases or mention alternatives. The guidance is minimal and inferred.

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