Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

domains_enableDomainLockV1

Enable domain lock to prevent unauthorized transfers by securing the domain and restricting registrar changes until the lock is disabled.

Instructions

Enable domain lock for the domain.

When domain lock is enabled, the domain cannot be transferred to another registrar without first disabling the lock.

Use this endpoint to secure domains against unauthorized transfers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name

Implementation Reference

  • TypeScript interface definition specifying the input parameters (domain: string) and response type for the 'domains_enableDomainLockV1' MCP tool. This is the schema for the tool.
      "domains_enableDomainLockV1": {
        params: {
          /**
           * Domain name
           */
          domain: string;
        };
        response: any; // Response structure will depend on the API
      };
    
      /**
       * Disable domain lock for the domain.
    
    Domain lock needs to be disabled before transferring the domain to another registrar.
    
    Use this endpoint to prepare domains for transfer to other registrars.
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 of behavioral disclosure. It explains the effect ('domain cannot be transferred') and security purpose, but lacks details on permissions needed, potential errors, or confirmation of success. This leaves 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 front-loaded with the main action, followed by explanatory context, and uses only three sentences with zero waste. Each sentence adds value without redundancy, making it highly efficient.

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 no annotations and no output schema, the description is adequate for a simple mutation tool but lacks completeness. It explains the purpose and effect but omits details on response format, error conditions, or integration with other tools, which could aid the agent in handling edge cases.

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

Parameters4/5

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

The schema description coverage is 100%, so the parameter 'domain' is documented in the schema. The description does not add specific details about the parameter, but since there is only one parameter and the schema fully covers it, a baseline of 4 is appropriate as no additional compensation is needed.

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 ('enable domain lock') and resource ('for the domain'), distinguishing it from sibling tools like 'domains_disableDomainLockV1' and 'domains_getDomainDetailsV1'. It precisely defines what the tool does without being tautological.

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 for when to use this tool ('to secure domains against unauthorized transfers') and implicitly contrasts with disabling the lock. However, it does not explicitly name alternatives or specify prerequisites, such as domain ownership verification, 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