Repository navigation
DNS_deleteDNSRecordsV1 can't delete anything: filters is not exposed and DELETE params are sent as query string (API requires a JSON body) #72
Description
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
- Have a domain with at least one record, e.g. an
Arecord namedgw. - Call
DNS_deleteDNSRecordsV1with{ "domain": "example.com" }(the only parameter the schema allows). - The API answers 422. Passing an extra
filtersargument also fails (it is not in the schema, and it would be sent as query string anyway).
Root cause (two parts)
- Schema: in
src/core/tools/all.js(anddns.js), theinputSchemaofDNS_deleteDNSRecordsV1only declaresdomain. The request body defined by the API is not included. - Transport: in
src/core/runtime.js,executeApiCalldoes:so any non-path parameter of aif (["GET", "DELETE"].includes(method)) { config.params = { ...(config.params || {}), ...requestParams }; // query string }
DELETEgoes to the
Activity
stjepandumancic-design commentedon Oct 29, 2026
Confirmed on the hosted OAuth MCP server (
https://mcp.hostinger.com) on 2026-10-29, using Codex CLI. This also affects the current search/execute operation interface.searchreturns operationdns_records_deletewith an input schema containing onlydomain(required). Nofiltersproperty is exposed.dns_records_listsucceeds in the same authenticated session.executewithoperation: "dns_records_delete"andparamscontaining bothdomainand explicit name/typefiltersreturns HTTP 422:The filters field is required.Sanitized request shape (example domain only):
{ "operation": "dns_records_delete", "params": { "domain": "example.com", "filters": [ {"name": "shop", "type": "A"}, {"name": "shop", "type": "AAAA"} ] } }Please expose the
filtersarray in the hosted operation schema and ensure it reaches the DNS DELETE endpoint as a JSON request body. The current failure is observable; the exact internal transport behavior of the hosted server has not been inspected in this confirmation.