Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

VPS_createPostInstallScriptV1

Automate VPS setup tasks by creating a post-install script that executes after virtual machine installation. The script is saved as /post_install and logs output to /post_install.log.

Instructions

Add a new post-install script to your account, which can then be used after virtual machine installation.

The script contents will be saved to the file /post_install with executable attribute set and will be executed once virtual machine is installed. The output of the script will be redirected to /post_install.log. Maximum script size is 48KB.

Use this endpoint to create automation scripts for VPS setup tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesContent of the script
nameYesName of the script

Implementation Reference

  • TypeScript interface definition for the input schema of the VPS_createPostInstallScriptV1 tool. Defines parameters: name (string) and content (string), with response as any.
    "VPS_createPostInstallScriptV1": {
      params: {
        /**
         * Name of the script
         */
        name: string;
        /**
         * Content of the script
         */
        content: string;
      };
      response: any; // Response structure will depend on the API
    };
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it specifies where the script is saved (/post_install), that it becomes executable, when it executes (after VM installation), where output goes (/post_install.log), and the 48KB size limit. It doesn't mention error handling or permissions requirements, but covers most essential operational details.

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 efficiently structured with three sentences that each earn their place: first states the purpose, second provides critical implementation details, third gives usage context. No wasted words, and key information is front-loaded.

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

Completeness4/5

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

For a creation tool with no annotations and no output schema, the description provides substantial context about what happens after creation (file location, execution timing, output redirection, size limits). It doesn't specify what the tool returns upon success or error conditions, but covers the essential operational behavior well given the complexity.

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 the schema already documents both parameters (name and content). The description doesn't add specific meaning beyond what the schema provides, such as format requirements or naming conventions for the 'name' parameter. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 specific action ('Add a new post-install script'), resource ('to your account'), and purpose ('which can then be used after virtual machine installation'). It distinguishes from sibling tools like VPS_deletePostInstallScriptV1 and VPS_updatePostInstallScriptV1 by focusing on creation rather than deletion or modification.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('to create automation scripts for VPS setup tasks') and implies usage after VM installation. However, it doesn't explicitly state when not to use it or name specific alternatives like VPS_updatePostInstallScriptV1 for modifying existing scripts.

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

Related 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