Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

billing_createServiceOrderV1

Create a new service order for hosting services by specifying payment method, items, and optional coupons. Orders are set for automatic renewal. Use alternative payment methods to avoid credit card verification issues.

Instructions

Create a new service order.

DEPRECATED

To purchase a domain, use POST /api/domains/v1/portfolio instead.

To purchase a VPS, use POST /api/vps/v1/virtual-machines instead.

To place order, you need to provide payment method ID and list of price items from the catalog endpoint together with quantity. Coupons also can be provided during order creation.

Orders created using this endpoint will be set for automatic renewal.

Some credit_card payments might need additional verification, rendering purchase unprocessed. We recommend use other payment methods than credit_card if you encounter this issue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
couponsNoDiscount coupon codes
itemsYesitems parameter
payment_method_idYesPayment method ID

Implementation Reference

  • Schema definition for the 'billing_createServiceOrderV1' tool, including input parameters (payment_method_id, items, coupons) and deprecation notice. This is part of the APITools interface defining MCP tool schemas.
      /**
       * Create a new service order. 
    
    **DEPRECATED**
    
    To purchase a domain, use [`POST /api/domains/v1/portfolio`](/#tag/domains-portfolio/POST/api/domains/v1/portfolio) instead.
    
    To purchase a VPS, use [`POST /api/vps/v1/virtual-machines`](/#tag/vps-virtual-machine/POST/api/vps/v1/virtual-machines) instead.
    
    
    To place order, you need to provide payment method ID and list of price items from the catalog endpoint together with quantity.
    Coupons also can be provided during order creation.
    
    Orders created using this endpoint will be set for automatic renewal.
    
    Some `credit_card` payments might need additional verification, rendering purchase unprocessed.
    We recommend use other payment methods than `credit_card` if you encounter this issue.
       */
      "billing_createServiceOrderV1": {
        params: {
          /**
           * Payment method ID
           */
          payment_method_id: number;
          /**
           * items parameter
           */
          items: array;
          /**
           * Discount coupon codes
           */
          coupons?: array;
        };
        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 the full burden of behavioral disclosure. It effectively describes key behaviors: orders will be set for automatic renewal, credit_card payments may need verification (rendering purchase unprocessed), and recommends alternative payment methods. However, it doesn't mention error handling, response format, or authentication requirements.

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 well-structured with clear sections (purpose, deprecation warning, usage requirements, behavioral notes). Most sentences earn their place, though the deprecation section is somewhat lengthy. It's appropriately sized for the complexity of a deprecated creation tool with behavioral nuances.

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?

Given this is a deprecated creation tool with no annotations and no output schema, the description provides good contextual coverage: purpose, deprecation status with alternatives, parameter requirements, and key behavioral traits (automatic renewal, payment method issues). It could be more complete by mentioning response format or error handling, but covers the essentials well.

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 all parameters. The description adds some context about what to provide ('payment method ID and list of price items from the catalog endpoint together with quantity' and 'coupons also can be provided'), but doesn't add significant meaning beyond what the schema provides. Baseline 3 is appropriate when 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 ('Create a new service order') and resource ('service order'), distinguishing it from siblings like billing_cancelSubscriptionV1 or billing_getCatalogItemListV1. The first sentence directly answers 'what does this tool do?' with no ambiguity.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when NOT to use this tool (deprecated for domain/VPS purchases with specific alternatives named) and when to use it (for service orders with payment method and catalog items). It clearly distinguishes this from sibling tools by specifying its deprecated status and alternatives.

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