patch_v1_tracker_projects_key_issues_num

UpdateIssue edits one issue in place and returns it — retitle it, rewrite its body, move it between board columns, reprioritize, reassign, or replace its labels.

UpdateIssue edits one issue in place and returns it — retitle it, rewrite its body, move it between board columns, reprioritize, reassign, or replace its labels. Every field is optional: one the caller omits keeps its stored value, and labels REPLACES the set rather than adding to it.

The issue's kind, source and git bindings are not editable here: they record where the work item came FROM, which is a fact about its origin rather than its current state.


Tool	`patch_v1_tracker_projects_key_issues_num`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	8
Operation	`PATCH /v1/tracker/projects/{key}/issues/{num}`
Product	tracker

Arguments

Field	Type	Required	Default	Description
`assignee`	`string`	—	—	Assignee is who owns the issue, at most 256 characters. Empty unassigns it.
`description`	`string`	—	—	Description is the issue body, at most 32768 characters.
`key`	`string`	—	—	Key is the issue's project, from the path.
`labels`	`string[]`	—	—	Labels REPLACES the issue's labels with exactly this set. Each label is at most 48 characters and may not contain a comma (the storage separator); empty entries are dropped.
`num`	`integer`	—	—	Num is the issue's number within that project, from the path.
`priority`	`string`	—	—	Priority is none, urgent, high, medium or low. Empty resets it to none.
`status`	`string`	—	—	Status moves the issue between board columns: backlog, todo, in_progress, done or canceled. Empty resets it to backlog.
`title`	`string`	—	—	Title is the issue's one-line summary. Non-empty, at most 512 characters.

This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.

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": "patch_v1_tracker_projects_key_issues_num",
         "arguments": {
           "assignee": "<assignee>",
           "description": "<description>",
           "key": "<key>",
           "labels": [
             "<labels>"
           ],
           "num": 0,
           "priority": "<priority>",
           "status": "<status>",
           "title": "<title>"
         }
       }
     }'

Values are placeholders derived from each field's declared type. 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
`cloud_patch_v1_tracker_projects_key_issues_num`	`PATCH /v1/tracker/projects/{key}/issues/{num}`	tracker	UpdateIssue edits one issue in place and returns it — retitle it, rewrite its body, move i

The same capability over plain HTTP is in the tracker API reference, on https://api.hanzo.ai.

All 834 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).

patch_v1_tracker_projects_key_issues_num

Arguments

Call it

The operation behind it

On this page