delete_v1_search_name
DropSearch deletes one search index from the shared backend and removes its metadata row.
DropSearch deletes one search index from the shared backend and removes its metadata row. Answers 204 with no body; a second call is a 404.
| Tool | delete_v1_search_name |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 1, 1 required |
| Operation | DELETE /v1/search/{name} |
| Product | search |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
name | string | yes | — | — | Name is the resource's org-unique slug, from the path. Lower-cased and trimmed before lookup, exactly as it was at create. |
tools/list declares a type and a description for each field and nothing further. The Required column is taken from DELETE /v1/search/{name}, the operation this tool dispatches to — the same declaration the REST API validates against. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "delete_v1_search_name",
"arguments": {
"name": "<name>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
delete_v1_search_name | DELETE /v1/search/{name} | search | Deletes one search index from the shared backend and removes its metadata row. |
The same capability over plain HTTP is in the search API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?