Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

DNS_getDNSRecordsV1

Fetch DNS zone records for a domain to view current DNS configuration and manage domain settings.

Instructions

Retrieve DNS zone records for a specific domain.

Use this endpoint to view current DNS configuration for domain management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name

Implementation Reference

  • Schema/registration definition for DNS_getDNSRecordsV1 tool. Defines the tool name, description, HTTP method (GET), path (/api/dns/v1/zones/{domain}), input schema (requires 'domain' parameter), and security configuration. This is a standard API tool (not custom) that gets routed through executeApiCall.
    {
      "name": "DNS_getDNSRecordsV1",
      "description": "Retrieve DNS zone records for a specific domain.\n\nUse this endpoint to view current DNS configuration for domain management.",
      "method": "GET",
      "path": "/api/dns/v1/zones/{domain}",
      "inputSchema": {
        "type": "object",
        "properties": {
          "domain": {
            "type": "string",
            "description": "Domain name"
          }
        },
        "required": [
          "domain"
        ]
      },
      "security": [
        {
          "apiToken": []
        }
      ],
      "group": "dns"
    },
  • Registration: The tool is registered as part of the dns tool list export in src/core/tools/dns.ts. It is imported by src/servers/dns.ts and passed to startServer(), which initializes the MCPServer with all tools in the list. The tool is not 'custom', so it flows through executeApiCall in runtime.js.
    {
      "name": "DNS_getDNSRecordsV1",
      "description": "Retrieve DNS zone records for a specific domain.\n\nUse this endpoint to view current DNS configuration for domain management.",
      "method": "GET",
      "path": "/api/dns/v1/zones/{domain}",
      "inputSchema": {
        "type": "object",
        "properties": {
          "domain": {
            "type": "string",
            "description": "Domain name"
          }
        },
        "required": [
          "domain"
        ]
      },
      "security": [
        {
          "apiToken": []
        }
      ],
      "group": "dns"
    },
  • Handler: The actual execution handler for DNS_getDNSRecordsV1 is the executeApiCall method in MCPServer. Since this tool has custom=false (not in the switch/case), it goes through executeApiCall which substitutes the {domain} path parameter from the request params, then makes a GET request to /api/dns/v1/zones/{domain} with the domain as a query parameter.
    async executeApiCall(tool, params) {
      // Get method and path from tool
      const method = tool.method;
      let path = tool.path;
    
      // Clone params to avoid modifying the original
      const requestParams = { ...params };
    
      // Replace path parameters with values from params
      Object.entries(requestParams).forEach(([key, value]) => {
        const placeholder = `{${key}}`;
        if (path.includes(placeholder)) {
          path = path.replace(placeholder, encodeURIComponent(String(value)));
          delete requestParams[key]; // Remove used parameter
        }
      });
    
      // Build the full URL
      const baseUrl = this.baseUrl.endsWith("/") ? this.baseUrl : `${this.baseUrl}/`;
      const cleanPath = path.startsWith("/") ? path.slice(1) : path;
      const url = new URL(cleanPath, baseUrl).toString();
    
      this.log('debug', `API Request: ${method} ${url}`);
    
      try {
        // Configure the request
        const config = {
          method: method.toLowerCase(),
          url,
          headers: { ...this.headers },
          timeout: 60000, // 60s
          validateStatus: function (status) {
            return status < 500; // Resolve only if the status code is less than 500
          }
        };
      
        const bearerToken = process.env['API_TOKEN'] || process.env['APITOKEN']; // APITOKEN for backwards compatibility
        if (bearerToken) {
          config.headers['Authorization'] = `Bearer ${bearerToken}`;
        } else {
          this.log('error', `Bearer Token environment variable not found: API_TOKEN`);
        }
    
        // Add parameters based on request method
        if (["GET", "DELETE"].includes(method)) {
          // For GET/DELETE, send params as query string
          config.params = { ...(config.params || {}), ...requestParams };
        } else {
          // For POST/PUT/PATCH, send params as JSON body
          config.data = requestParams;
          config.headers["Content-Type"] = "application/json";
        }
    
        this.log('debug', "Request config:", {
          url: config.url,
          method: config.method,
          params: config.params,
          headers: Object.keys(config.headers)
        });
    
        // Execute the request
        const response = await axios(config);
        this.log('debug', `Response status: ${response.status}`);
    
        return response.data;
    
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        this.log('error', `API request failed: ${errorMessage}`);
    
        if (axios.isAxiosError(error)) {
          const responseData = error.response?.data;
          const responseStatus = error.response?.status;
    
          this.log('error', 'API Error Details:', {
            status: responseStatus,
            data: typeof responseData === 'object' ? JSON.stringify(responseData) : responseData
          });
    
          // Rethrow with more context for better error handling
          const detailedError = new Error(`API request failed with status ${responseStatus}: ${errorMessage}`);
          detailedError.response = error.response;
          throw detailedError;
        }
    
        throw error;
      }
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states it retrieves records, with no mention of read-only nature, authentication needs, rate limits, or response format. The description lacks important behavioral context.

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?

Two sentences that are mostly direct and front-loaded. The second sentence ('Use this endpoint to view current DNS configuration for domain management') is slightly redundant with the first, but overall concise.

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?

For a read tool with one parameter and no output schema, the description should explain what the response contains (types of records) and any constraints. It does not, leaving the agent with incomplete context.

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 coverage is 100% with the single parameter 'domain' described as 'Domain name'. The description adds no additional meaning beyond this, so baseline score of 3 is appropriate.

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 verb ('Retrieve'), resource ('DNS zone records'), and scope ('for a specific domain'). It distinguishes from sibling DNS write/management tools by specifying 'view current DNS configuration for domain management.'

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 implies usage for viewing DNS configuration but does not provide explicit when-not-to-use guidance or mention alternatives among the many sibling DNS tools.

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

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