Summary

DNS_deleteDNSRecordsV1 always fails with HTTP 422. There is no way to tell the tool which record to delete, and even if there were, the parameter would not reach the API in the right place.

Tested with @hostinger/mcp 1.63.3 (latest) and with the hosted connector at mcp.hostinger.com (same behavior).

Steps to reproduce

1. Have a domain with at least one record, e.g. an A record named gw.
2. Call DNS_deleteDNSRecordsV1 with { "domain": "example.com" } (the only parameter the schema allows).
3. The API answers 422. Passing an extra filters argument also fails (it is not in the schema, and it would be sent as query string anyway).

Root cause (two parts)

1. Schema: in src/core/tools/all.js (and dns.js), the inputSchema of DNS_deleteDNSRecordsV1 only declares domain. The request body defined by the API is not included.
2. Transport: in src/core/runtime.js, executeApiCall does:

   if (["GET", "DELETE"].includes(method)) {
     config.params = { ...(config.params || {}), ...requestParams }; // query string
   }

   so any non-path parameter of a DELETE goes to the