MCP tools

type_update write

Rename a type, change its tag or description, switch it between work item and document, or delete it. Switching the behaviour of a type in use changes the layout of every issue carrying it. The issue type is the default for new issues: it is always a work item and cannot be deleted. A type a live issue carries cannot be deleted either; the refusal says how many, so retype them with issue_update first. Only an admin may change a type. delete cannot be combined with anything else.

Arguments

NameTypeDescription
deletebooleandelete the type instead of changing it. Refused for the issue type and for a type a live issue carries: retype those issues first. Cannot be combined with another change
descriptionnull | stringa new one-line description
is_documentnull | booleanswitch the type between work item (false) and document (true). The issue type is always a work item
namenull | stringa new name; the key does not follow it
tagnull | stringa new tag, one to five letters or digits, uppercased
type requiredstringthe type's key such as spec, or its ULID; read roadmap://types

Input schema

Exactly what tools/list serves.

input schema
{
  "additionalproperties": false,
  "properties": {
    "delete": {
      "description": "delete the type instead of changing it. Refused for the issue type and for a type a live issue carries: retype those issues first. Cannot be combined with another change",
      "type": "boolean"
    },
    "description": {
      "description": "a new one-line description",
      "type": [
        "null",
        "string"
      ]
    },
    "is_document": {
      "description": "switch the type between work item (false) and document (true). The issue type is always a work item",
      "type": [
        "null",
        "boolean"
      ]
    },
    "name": {
      "description": "a new name; the key does not follow it",
      "type": [
        "null",
        "string"
      ]
    },
    "tag": {
      "description": "a new tag, one to five letters or digits, uppercased",
      "type": [
        "null",
        "string"
      ]
    },
    "type": {
      "description": "the type's key such as spec, or its ULID; read roadmap://types",
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}