Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

VPS_createNewProjectV1

Deploy or replace Docker Compose projects on a virtual machine by providing a URL or raw YAML content. Supports GitHub repositories and custom docker-compose.yaml files for streamlined project setup.

Instructions

Deploy new project from docker-compose.yaml contents or download contents from URL.

URL can be Github repository url in format https://github.com/[user]/[repo] and it will be automatically resolved to docker-compose.yaml file in master branch. Any other URL provided must return docker-compose.yaml file contents.

If project already exists, it will be replaced.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesURL pointing to docker-compose.yaml file, Github repository or raw YAML content of the compose file
project_nameYesDocker Compose project name using alphanumeric characters, dashes, and underscores only
virtualMachineIdYesVirtual Machine ID

Implementation Reference

  • TypeScript interface definition for the 'VPS_createNewProjectV1' tool schema, including parameters (virtualMachineId, project_name, content, optional environment) and generic response.
    "VPS_createNewProjectV1": {
      params: {
        /**
         * Virtual Machine ID
         */
        virtualMachineId: number;
        /**
         * Docker Compose project name using alphanumeric characters, dashes, and underscores only
         */
        project_name: string;
        /**
         * URL pointing to docker-compose.yaml file, Github repository or raw YAML content of the compose file
         */
        content: string;
        /**
         * Project environment variables
         */
        environment?: string;
      };
      response: any; // Response structure will depend on the API
    };
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: it's a deployment tool (implies mutation), handles URL resolution for GitHub repositories, and replaces existing projects. However, it doesn't mention authentication requirements, rate limits, error conditions, or what happens during deployment (e.g., downtime).

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 appropriately sized and front-loaded with the core purpose. Each sentence adds value: first states the main action, second explains URL handling, third clarifies replacement behavior. There's minimal waste, though the GitHub format explanation could be slightly more concise.

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 deployment tool with 3 parameters, 100% schema coverage, but no annotations and no output schema, the description is moderately complete. It covers the main functionality and parameter usage but lacks details about return values, error handling, side effects, and integration with sibling tools like VPS_getProjectListV1.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful context beyond the schema: it explains that 'content' can be raw YAML or a URL, specifies GitHub URL format requirements, and clarifies that other URLs must return docker-compose.yaml contents. This provides valuable semantic understanding of the 'content' parameter.

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 tool's purpose with specific verbs ('deploy new project') and resources ('from docker-compose.yaml contents or download contents from URL'). It distinguishes itself from sibling tools like VPS_updateProjectV1 and VPS_deleteProjectV1 by focusing on initial deployment rather than modification or removal.

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 provides some implied usage context by specifying acceptable URL formats and stating that existing projects will be replaced. However, it doesn't explicitly guide when to use this tool versus alternatives like VPS_updateProjectV1 or mention prerequisites such as needing an existing virtual machine.

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