Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

domains_createWHOISProfileV1

Generate a WHOIS contact profile for domain registration by specifying TLD, country code, entity type, and WHOIS details. Streamlines the process of adding accurate contact information for domain setup.

Instructions

Create WHOIS contact profile.

Use this endpoint to add new contact information for domain registration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesISO 3166 2-letter country code
entity_typeYesLegal entity type
tldYesTLD of the domain (without leading dot)
tld_detailsNoTLD details
whois_detailsYesWHOIS details

Implementation Reference

  • TypeScript interface definition for the 'domains_createWHOISProfileV1' tool schema, specifying input parameters (tld, country, entity_type, tld_details, whois_details) and generic response.
    "domains_createWHOISProfileV1": {
      params: {
        /**
         * TLD of the domain (without leading dot)
         */
        tld: string;
        /**
         * ISO 3166 2-letter country code
         */
        country: string;
        /**
         * Legal entity type
         */
        entity_type: string;
        /**
         * TLD details
         */
        tld_details?: object;
        /**
         * WHOIS details
         */
        whois_details: object;
      };
      response: any; // Response structure will depend on the API
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Create' and 'add new contact information,' implying a write operation, but fails to disclose critical details like required permissions, whether the operation is idempotent, error handling, or what happens on success. This leaves significant gaps for a mutation tool.

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 extremely concise with just two sentences, front-loaded with the core purpose and followed by a usage hint. Every word earns its place, with no redundant or verbose language, making it efficient and easy to parse.

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

Completeness2/5

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

Given the complexity of a mutation tool with 5 parameters (including nested objects) and no annotations or output schema, the description is incomplete. It lacks details on behavioral traits, error cases, return values, and how parameters interact, making it insufficient for safe and effective use by an AI agent.

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 thoroughly. The description adds no additional parameter semantics beyond what's in the schema, such as explaining relationships between parameters or usage examples. This meets the baseline for high schema coverage but doesn't add extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Create') and resource ('WHOIS contact profile'), and it distinguishes the action from general domain operations. However, it doesn't explicitly differentiate from sibling tools like 'domains_getWHOISProfileV1' or 'domains_deleteWHOISProfileV1', which would be needed for a perfect score.

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

Usage Guidelines3/5

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

The description provides implied usage context by stating 'Use this endpoint to add new contact information for domain registration,' which suggests it's for setting up domain registration details. However, it lacks explicit guidance on when to use this versus alternatives (e.g., updating vs. creating) or any prerequisites, keeping it at a basic level.

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