hostinger-api-mcp 1.35.5 → 1.36.0

package/types.d.ts

@@ -7,7 +7,7 @@ export interface APITools {
   /**
    * Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For plain PHP applications that should be extracted as-is, use agencyHosting_deployPhpApplication instead. The website UID is automatically resolved from the domain.
    */
-  "agencyHosting_deployNodeStaticWebsite": {
+  "agency-hosting_deployNodeStaticWebsite": {
     params: {
       /**
        * Domain name of the Agency Plan website (e.g., example.com)
@@ -28,7 +28,7 @@ export interface APITools {
   /**
    * Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For node-static websites that require a build step, use agencyHosting_deployNodeStaticWebsite instead. The website UID is automatically resolved from the domain.
    */
-  "agencyHosting_deployPhpApplication": {
+  "agency-hosting_deployPhpApplication": {
     params: {
       /**
        * Domain name of the Agency Plan website (e.g., example.com)
@@ -209,7 +209,7 @@ Each datacenter includes a `pinger_url` you can ping from the client to measure
 latency; comparing the results across datacenters lets you pick the nearest one (lowest
 ping) before choosing its `code` as the `datacenter_code` when creating a website setup.
    */
-  "agency-hosting_listAvailableDatacentersForAnAgencyPlanOrderV1": {
+  "agency-hosting_listAvailableDatacentersV1": {
     params: {
       /**
        * Agency Plan order ID
@@ -225,7 +225,7 @@ ping) before choosing its `code` as the `datacenter_code` when creating a websit
 Provide the current domain in the path and the new domain in the request body.
 Set domain to null to revert to the temporary domain.
    */
-  "agency-hosting_changeAgencyPlanWebsiteDomainV1": {
+  "agency-hosting_changeWebsiteDomainV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -246,7 +246,7 @@ Set domain to null to revert to the temporary domain.
   /**
    * Links a domain to the specified Agency Plan website so it can serve traffic for that domain.
    */
-  "agency-hosting_linkDomainToAgencyPlanWebsiteV1": {
+  "agency-hosting_linkDomainToWebsiteV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -265,7 +265,7 @@ Set domain to null to revert to the temporary domain.
 
 Use the website_uuids filter to narrow results to specific websites.
    */
-  "agency-hosting_listAgencyPlanDomainsV1": {
+  "agency-hosting_listDomainsV1": {
     params: {
       /**
        * Page number
@@ -292,7 +292,7 @@ Website files and database are preserved, and any other linked domains remain ac
 
 If this is the only domain on the website, unlinking leaves the website without an accessible domain.
    */
-  "agency-hosting_unlinkDomainFromAgencyPlanWebsiteV1": {
+  "agency-hosting_unlinkDomainFromWebsiteV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -313,7 +313,7 @@ Upload the archive to the website's root directory via file browser first, then
 filename in this request. Website contents are overwritten by the archive contents. Supported
 archive types: .zip, .tar, .tar.gz, .tgz.
    */
-  "agency-hosting_importAgencyPlanWebsiteFromArchiveV1": {
+  "agency-hosting_importWebsiteFromArchiveV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -330,7 +330,7 @@ archive types: .zip, .tar, .tar.gz, .tgz.
   /**
    * Returns a paginated list of Agency Plan orders accessible to the authenticated client.
    */
-  "agency-hosting_listAgencyPlanOrdersV1": {
+  "agency-hosting_listOrdersV1": {
     params: {
       /**
        * Page number
@@ -363,7 +363,7 @@ Common setups:
 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.
    */
-  "agency-hosting_provisionANewAgencyPlanWebsiteV1": {
+  "agency-hosting_createANewWebsiteV1": {
     params: {
       /**
        * Agency Plan order ID
@@ -412,7 +412,7 @@ endpoint.
 Poll this endpoint using the `setup_uuid` returned from the provisioning request until
 `status` becomes `completed`, at which point `website_uid` identifies the new website.
    */
-  "agency-hosting_getAgencyPlanWebsiteSetupStatusV1": {
+  "agency-hosting_getWebsiteSetupStatusV1": {
     params: {
       /**
        * Agency Plan order ID
@@ -432,7 +432,7 @@ Poll this endpoint using the `setup_uuid` returned from the provisioning request
 Upload the archive to file browser first, then provide its relative path from document root in this request.
 Website contents are overwritten by the build result, which is deployed to public_html.
    */
-  "agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1": {
+  "agency-hosting_buildWebsiteNodeJSAssetsV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -451,7 +451,7 @@ Website contents are overwritten by the build result, which is deployed to publi
 
 This operation clears all cache types for the website.
    */
-  "agency-hosting_clearAgencyPlanWebsiteCacheV1": {
+  "agency-hosting_clearWebsiteCacheV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -466,7 +466,7 @@ This operation clears all cache types for the website.
 
 Each entry includes the schedule expression and the command executed on that schedule.
    */
-  "agency-hosting_listAgencyPlanWebsiteCronJobsV1": {
+  "agency-hosting_listWebsiteCronJobsV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -489,7 +489,7 @@ Each entry includes the schedule expression and the command executed on that sch
 
 Returns the created cron job, including its uuid, which is required to delete the cron job.
    */
-  "agency-hosting_createAgencyPlanWebsiteCronJobV1": {
+  "agency-hosting_createWebsiteCronJobV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -512,7 +512,7 @@ Returns the created cron job, including its uuid, which is required to delete th
 
 The operation is idempotent: deleting a cron job that does not exist succeeds without error.
    */
-  "agency-hosting_deleteAgencyPlanWebsiteCronJobV1": {
+  "agency-hosting_deleteWebsiteCronJobV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -531,7 +531,7 @@ The operation is idempotent: deleting a cron job that does not exist succeeds wi
 
 Each entry includes the database's non-system users.
    */
-  "agency-hosting_listAgencyPlanWebsiteDatabasesV1": {
+  "agency-hosting_listWebsiteDatabasesV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -554,7 +554,7 @@ Each entry includes the database's non-system users.
 
 The database name, username, and password must all be provided by the caller.
    */
-  "agency-hosting_createAgencyPlanWebsiteDatabaseV1": {
+  "agency-hosting_createWebsiteDatabaseV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -581,7 +581,7 @@ The database name, username, and password must all be provided by the caller.
 
 The operation is idempotent: deleting a database that does not exist succeeds without error.
    */
-  "agency-hosting_deleteAgencyPlanWebsiteDatabaseV1": {
+  "agency-hosting_deleteWebsiteDatabaseV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -600,7 +600,7 @@ The operation is idempotent: deleting a database that does not exist succeeds wi
 
 Each database supports a single non-system user; creating a user for a database that already has one fails.
    */
-  "agency-hosting_createAgencyPlanWebsiteDatabaseUserV1": {
+  "agency-hosting_createWebsiteDatabaseUserV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -631,7 +631,7 @@ Each database supports a single non-system user; creating a user for a database
 
 The operation is idempotent: deleting a user that does not exist succeeds without error.
    */
-  "agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1": {
+  "agency-hosting_deleteWebsiteDatabaseUserV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -653,7 +653,7 @@ The operation is idempotent: deleting a user that does not exist succeeds withou
    * Retrieves detailed information about a specific Agency Plan website, including configuration,
 status, metadata, hosting plan details, and resource quotas.
    */
-  "agency-hosting_getAgencyPlanWebsiteDetailsV1": {
+  "agency-hosting_getWebsiteDetailsV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -668,7 +668,7 @@ status, metadata, hosting plan details, and resource quotas.
 website is immediately transitioned to a deleting state and the underlying server
 resources are removed in the background.
    */
-  "agency-hosting_deleteAgencyPlanWebsiteV1": {
+  "agency-hosting_deleteWebsiteV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -684,7 +684,7 @@ resources are removed in the background.
 Each process has a unique ID (for tracking), a type, and a status (running, completed, failed).
 Poll this endpoint after initiating async operations (SSL setup, backups, cloning) to track progress.
    */
-  "agency-hosting_listRunningAgencyPlanWebsiteProcessesV1": {
+  "agency-hosting_listWebsiteProcessesV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -697,7 +697,7 @@ Poll this endpoint after initiating async operations (SSL setup, backups, clonin
   /**
    * Changes the installed WordPress core version on an Agency Plan website to one of the versions available for installation.
    */
-  "agency-hosting_changeAgencyPlanWebsiteWordPressCoreVersionV1": {
+  "agency-hosting_changeWordPressVersionV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -715,7 +715,7 @@ Poll this endpoint after initiating async operations (SSL setup, backups, clonin
    * Returns the current WordPress settings for an Agency Plan website: installed core version,
 LiteSpeed Cache plugin status, object cache status, and maintenance mode status.
    */
-  "agency-hosting_getAgencyPlanWebsiteWordPressSettingsV1": {
+  "agency-hosting_getWordPressSettingsV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -728,7 +728,7 @@ LiteSpeed Cache plugin status, object cache status, and maintenance mode status.
   /**
    * Lists the WordPress core versions available for installation on an Agency Plan website.
    */
-  "agency-hosting_listAvailableWordPressVersionsForAnAgencyPlanWebsiteV1": {
+  "agency-hosting_listAvailableWordPressVersionsV1": {
     params: {
       /**
        * Agency Plan website UID
@@ -1937,6 +1937,24 @@ the Ecommerce API.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Returns a signed URL to upload a product image to (multipart/form-data POST). Then call the
+attach-image endpoint with the returned object_name to scan and attach it to the product.
+   */
+  "ecommerce_createAProductImageUploadURLV1": {
+    params: {
+      /**
+       * The ID of the store the product belongs to.
+       */
+      store_id: string;
+      /**
+       * The ID of the product the image will be attached to.
+       */
+      product_id: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Create a published digital product with a single variant and an optional external download link.
    */
@@ -2000,9 +2018,9 @@ the Ecommerce API.
   };
 
   /**
-   * Upload a raster image (JPEG, PNG, GIF or WebP, max 15MB) and attach it to a product in a single call.
-The image is virus-scanned and validated by content, then stored on the CDN. Set is_thumbnail to make
-it the product's primary image.
+   * Fetch a raster image (JPEG, PNG, GIF or WebP, max 15MB) from a URL and attach it to a product in a
+single call. The image is virus-scanned and validated by content, then stored on the CDN. Set
+is_thumbnail to make it the product's primary image.
    */
   "ecommerce_uploadAndAttachAProductImageV1": {
     params: {
@@ -2015,9 +2033,15 @@ it the product's primary image.
        */
       product_id: string;
       /**
-       * Raster image file (JPEG, PNG, GIF or WebP), maximum 15MB. SVG is not accepted.
+       * Publicly reachable URL of the raster image (JPEG, PNG, GIF or WebP), maximum 15MB. The image is
+fetched, virus-scanned and validated by content, then stored on the CDN. SVG is not accepted.
+Provide either this or object_name.
        */
-      image: string;
+      image_url?: string;
+      /**
+       * Key returned by the upload-url endpoint. Provide this instead of image_url to attach an uploaded image.
+       */
+      object_name?: string;
       /**
        * When true, the image becomes the product's thumbnail (primary image). When omitted, it becomes the
 thumbnail only if the product does not have one yet.
@@ -4322,6 +4346,84 @@ requests are rate limited upstream.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Get a single automation with the counts of contacts that entered it, are moving through it,
+finished it or failed on the way.
+
+This describes the automation itself. To see the workflow it runs, use the steps endpoint.
+   */
+  "reach_getAutomationDetailsV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Automation uuid parameter
+       */
+      automationUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Get a paginated list of the automations in a profile.
+
+Every automation comes with the counts of contacts that entered it, are moving through it,
+finished it or failed on the way. Those counts describe the contact journey and are not
+email engagement metrics - for opens, clicks and unsubscribes use the campaign statistics
+endpoint instead.
+   */
+  "reach_listAutomationsV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Filter automations by status.
+
+There is no `completed` status. An automation that has finished for every contact still
+reports `active`.
+       */
+      status?: string;
+      /**
+       * Order automations by creation date. Newest first unless set to `asc`.
+       */
+      sort_direction?: string;
+      /**
+       * Page number
+       */
+      page?: number;
+      /**
+       * Number of items per page
+       */
+      per_page?: number;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Get the workflow of an automation as a flat list of steps.
+
+The steps form a tree rather than a straight line: follow `parent_uuid` to reconstruct the
+branches, and use `step_order` to order the steps that share a parent. An automation with no
+steps yet returns an empty list.
+   */
+  "reach_listAutomationStepsV1": {
+    params: {
+      /**
+       * Profile uuid parameter
+       */
+      profileUuid: string;
+      /**
+       * Automation uuid parameter
+       */
+      automationUuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Delete a contact with the specified UUID.