Skip to main content
Glama
hostinger

hostinger-api-mcp

Official
by hostinger
OverviewSchemaRelated ServersScoreDiscussions(1)
TypeScript
Remote

Create a new website

agency-hosting_createANewWebsiteV1

Create a new website on your Agency Plan by specifying datacenter, stack flavor, PHP version, and optional domain or WordPress settings. Returns a setup UUID for background provisioning.

Instructions

Provisions a new website on one of your Agency Plan hosting orders.

Choose the datacenter, stack (flavor), and PHP version for the site. Optionally attach your own domain — omit it, set it to null, or leave it unavailable and a free *.hostingersite.com subdomain is generated instead — and/or install WordPress by supplying the wordpress details (admin account, site title, and language).

Common setups:

  • Plain PHP site: flavor set to php-fpm, with settings.php.version; omit wordpress and type.

  • WordPress site: flavor set to the desired WordPress version (e.g. wp-7.0), plus the wordpress block (admin account, title, language).

  • Static/Node.js frontend app: flavor set to php-fpm and type set to node-static.

Provisioning runs in the background, so the response returns immediately with a setup UUID that identifies the job. The new website becomes reachable once provisioning finishes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoWebsite type
domainNoPrimary domain to attach to the website. Omit or set to null to get a free auto-generated *.hostingersite.com subdomain instead.
flavorYesSetup flavor: a specific WordPress version in the format `wp-<major>.<minor>` or `wp-<major>.<minor>.<patch>` (e.g. `wp-6.8.2`), or `php-fpm` for a plain PHP stack. Generic versions like `wp-latest` are not allowed.
order_idYesAgency Plan order ID
settingsYesWebsite settings
wordpressNoWordPress installation options
datacenter_codeYesDatacenter code where the website should be provisioned. Available codes depend on live capacity and are not a fixed set.

Schema Changelog

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

  1. Changed3 schema fields changedv1.55.1
    • removedInput schema / properties / clone
      Removed value: -{
-  "description": "Clone the new website from an existing website",
-  "properties": {
-    "website_uid": {
-      "description": "website_uid parameter",
-      "type": "string"
-    }
-  },
-  "required": [
-    "website_uid"
-  ],
-  "type": "object"
-}
    • removedInput schema / properties / derive_domain
      Removed value: -{
-  "description": "Derive the domain from an existing vhost",
-  "properties": {
-    "from_vhost": {
-      "description": "from_vhost parameter",
-      "properties": {
-        "username": {
-          "description": "username parameter",
-          "type": "string"
-        },
-        "vhost": {
-          "description": "vhost parameter",
-          "type": "string"
-        }
-      },
-      "required": [
-        "username",
-        "vhost"
-      ],
-      "type": "object"
-    }
-  },
-  "required": [
-    "from_vhost"
-  ],
-  "type": "object"
-}
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "horizons",
-  "node-static"
-]New value: +[
+  "node-static"
+]
  2. Addedv1.42.0

TDQS

A4.8/5.0
Behavior5/5

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

The description clearly discloses that provisioning is asynchronous: returns immediately with a setup UUID, website becomes reachable only after provisioning finishes. It also explains the domain fallback behavior. This adds substantial context beyond the sparse annotations (readOnlyHint=false, destructiveHint=false).

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 front-loaded with a one-sentence purpose, followed by compact bullet recipes and a clear closing note about background provisioning. There is no filler, and the structure makes the multi-setup complexity easy to parse.

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 7-parameter nested create tool with no output schema, the description covers all major invocation paths, the free subdomain behavior, and the asynchronous job identification. The only minor omission (datacenter codes depend on live capacity) is already present in the schema, so the total tool definition is complete.

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

Parameters5/5

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

Though schema coverage is 100%, the description adds crucial combinatorial meaning: how 'flavor' values map to PHP vs WordPress setups, how 'type'='node-static' creates a static frontend, and exactly what happens when 'domain' is omitted. These recipes go well beyond the schema's individual parameter descriptions.

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+resource: 'Provisions a new website on one of your Agency Plan hosting orders.' It details the key choices (datacenter, flavor, PHP version, domain, WordPress) and explicitly scopes to Agency Plan hosting, distinguishing it from sibling deploy/import tools.

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?

Provides concrete setup recipes (plain PHP, WordPress, static/Node.js) that tell an agent which parameter combinations work and when this tool is appropriate. However, it does not explicitly contrast with alternatives like agency-hosting_deployNodeStaticWebsite or hosting_installWordPressV1, so no clear exclusions or 'use X instead' guidance.

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