delete_v1_tracker_projects_key_issues_num
DeleteIssue removes one issue from a tracker project and answers 204 with no body. 404 when the project or the issue does not exist in the caller's org.
DeleteIssue removes one issue from a tracker project and answers 204 with no body. 404 when the project or the issue does not exist in the caller's org.
The issue's number is NOT reused: the next issue on the board takes the next number, so a deleted identifier stays retired rather than silently pointing at different work.
| Tool | delete_v1_tracker_projects_key_issues_num |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 2 required |
| Operation | DELETE /v1/tracker/projects/{key}/issues/{num} |
| Product | tracker |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
key | string | yes | — | — | Key is the issue's project, from the path. |
num | integer | yes | — | — | Num is the issue's number within that project — the digits of KEY-14. Positive; anything else is refused with 400. |
tools/list declares a type and a description for each field and nothing further. The Required column is taken from DELETE /v1/tracker/projects/{key}/issues/{num}, 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_tracker_projects_key_issues_num",
"arguments": {
"key": "<key>",
"num": 0
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. num holds a stand-in that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so that value is this page's, not the API's. Neither the door nor the operation 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_tracker_projects_key_issues_num | DELETE /v1/tracker/projects/{key}/issues/{num} | tracker | Removes one issue from a tracker project and answers 204 with no body. |
The same capability over plain HTTP is in the tracker 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?
delete_v1_tracker_projects_key
DeleteProject removes one tracker project of the caller's org AND every issue filed under it, and answers 204 with no body. 404 when the org has no project under that key.
get_v1_tracker_projects
ListProjects returns every tracker project in the caller's org, newest first.