get_v1_tracker_projects_key_issues_num
GetIssue returns one issue of one tracker project by its per-project number — title, description, status, priority, assignee, labels, kind, source and its git bindings.
GetIssue returns one issue of one tracker project by its per-project number — title, description, status, priority, assignee, labels, kind, source and its git bindings. 404 when the project or the issue does not exist in the caller's org.
| Tool | get_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 | GET /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 GET /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": "get_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 |
|---|---|---|---|
get_v1_tracker_projects_key_issues_num | GET /v1/tracker/projects/{key}/issues/{num} | tracker | Returns one issue of one tracker project by its per-project number — title, description,… |
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?
get_v1_tracker_projects_key_issues
ListIssues returns the issues of one tracker project, optionally filtered by status, kind, repo and source.
patch_v1_tracker_projects_key
UpdateProject renames a tracker project or rewrites its description, and returns the updated project. Both fields are optional: one the caller omits keeps its stored value.