Skip to main content
Glama
hostinger

hostinger-api-mcp

Official
by hostinger
OverviewSchemaRelated ServersScoreDiscussions(1)
TypeScript
Remote

Recreate virtual machine

VPS_recreateVirtualMachineV1
Destructive

Rebuild a VPS from scratch with a fresh OS installation, resetting the virtual machine to its initial state. Irreversibly deletes all data and snapshots, so use it when you need a clean server.

Instructions

Recreate a virtual machine from scratch.

The recreation process involves reinstalling the operating system and resetting the virtual machine to its initial state. Snapshots, if there are any, will be deleted.

Password Requirements

Password will be checked against leaked password databases. Requirements for the password are:

  • At least 12 characters long

  • At least one uppercase letter

  • At least one lowercase letter

  • At least one number

  • Is not leaked publicly

This operation is irreversible and will result in the loss of all data stored on the virtual machine!

Use this endpoint to completely rebuild VPS instances with fresh OS installation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordNoRoot password for the virtual machine. If not provided, random password will be generated. Password will not be shown in the response.
template_idYesTemplate ID
panel_passwordNoPanel password for the panel-based OS template. If not provided, random password will be generated. If OS does not support panel_password this field will be ignored. Password will not be shown in the response.
virtualMachineIdYesVirtual Machine ID
post_install_script_idNoPost-install script to execute after virtual machine was recreated

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.2.2
  2. Removedv0.2.1
  3. Changed3 schema fields changedv0.1.40
    • addedInput schema / properties / panel_password
      Added value: +{
+  "description": "Panel password for the panel-based OS template. If not provided, random password will be generated.\nIf OS does not support panel_password this field will be ignored.\nPassword will not be shown in the response.",
+  "type": "string"
+}
    • changedInput schema / properties / password / description
      Previous value: -"Password for the virtual machine. If not provided, random password will be generated. Password will not be shown in the response."New value: +"Root password for the virtual machine. If not provided, random password will be generated.\nPassword will not be shown in the response."
    • changedInput schema / properties / post_install_script_id / description
      Previous value: -"Post-install script ID"New value: +"Post-install script to execute after virtual machine was recreated"
  4. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this destructive, but the description goes further by disclosing that snapshots will be deleted, data is irreversibly lost, and the OS is reinstalled. It also reveals password validation against leaked databases, which is material behavioral context not available from annotations or schema.

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 appropriately sized for a destructive, high-stakes operation. Key information is front-loaded, the password requirements are scannable in bullets, and the irreversible data-loss warning is prominent. No sentence is filler.

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

Completeness5/5

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

For a destructive recreation operation with no output schema, the description covers the essential facts: what happens, what gets destroyed, irreversibility, and additional password constraints. An agent has enough information to invoke the tool correctly and to warn the user about consequences.

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?

The schema already documents all five parameters, so the baseline is 3. The description adds meaningful extra semantics for the password parameter by specifying length, character class, and leaked-database requirements, going beyond the schema's basic description.

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 opens with a specific verb and resource: 'Recreate a virtual machine from scratch.' It clarifies the operation by explaining it reinstalls the operating system and resets the VM to its initial state, which distinguishes it from ops like restarting, stopping, or purchasing a VM.

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 final line explicitly states when to use the endpoint: 'to completely rebuild VPS instances with fresh OS installation.' It gives clear context for use, though it does not explicitly name alternative tools or exclude non-recreation operations.

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