Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

domains_purchaseNewDomainV1

Purchase and register a new domain name. Automatically uses default payment or WHOIS details if not provided. Includes validation for TLD-specific registration data. Ideal for domain registration and management.

Instructions

Purchase and register a new domain name.

If registration fails, login to hPanel and check domain registration status.

If no payment method is provided, your default payment method will be used automatically.

If no WHOIS information is provided, default contact information for that TLD will be used. Before making request, ensure WHOIS information for desired TLD exists in your account.

Some TLDs require additional_details to be provided and these will be validated before completing purchase.

Use this endpoint to register new domains for users.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
additional_detailsNoAdditional registration data, possible values depends on TLD
couponsNoDiscount coupon codes
domainYesDomain name
domain_contactsNoDomain contact information
item_idYesCatalog price item ID
payment_method_idNoPayment method ID, default will be used if not provided

Implementation Reference

  • TypeScript interface definition for the input parameters and generic response type of the 'domains_purchaseNewDomainV1' MCP tool, auto-generated from OpenAPI specification. This defines the tool schema for purchasing and registering a new domain name.
    "domains_purchaseNewDomainV1": {
      params: {
        /**
         * Domain name
         */
        domain: string;
        /**
         * Catalog price item ID
         */
        item_id: string;
        /**
         * Payment method ID, default will be used if not provided
         */
        payment_method_id?: number;
        /**
         * Domain contact information
         */
        domain_contacts?: object;
        /**
         * Additional registration data, possible values depends on TLD
         */
        additional_details?: object;
        /**
         * Discount coupon codes
         */
        coupons?: array;
      };
      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 the full burden. It discloses key behavioral traits: the tool involves a financial transaction (purchase), may fail with registration issues, uses default payment methods and WHOIS info if not provided, and requires validation for some TLDs. However, it lacks details on error handling beyond a manual login suggestion, rate limits, or authentication requirements, leaving some gaps.

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 useful information, such as failure handling, defaults, and prerequisites, with minimal waste. However, the last sentence ('Use this endpoint to register new domains for users.') is somewhat redundant with the opening, slightly reducing efficiency.

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?

Given the complexity of a purchase tool with 6 parameters, no annotations, and no output schema, the description is moderately complete. It covers purpose, usage, and some behavioral aspects but lacks details on return values, error codes, or specific authentication needs. This makes it adequate but with clear gaps for a tool of this nature.

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 by explaining default behaviors for 'payment_method_id' and 'domain_contacts', and notes that 'additional_details' are TLD-dependent and validated. This provides marginal value beyond the schema, aligning with the baseline of 3 for high coverage.

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 explicitly states the verb 'purchase and register' and the resource 'a new domain name', making the purpose clear. It distinguishes this tool from sibling tools like 'domains_checkDomainAvailabilityV1' (which checks availability) and 'domains_getDomainListV1' (which lists domains), as this is the only tool for purchasing domains.

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 description provides clear context on when to use this tool ('to register new domains for users') and includes prerequisites like ensuring WHOIS information exists. However, it does not explicitly state when not to use it or name specific alternatives (e.g., 'domains_checkDomainAvailabilityV1' for checking availability first), which prevents a perfect score.

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