delete_support_by_id
Calls DELETE /api/support/{id} as the signed-in person · REST reference
Archive a support case (soft delete)
Platform-staff only (requirePlatformStaff). Backed by Mutation.archiveSupportCase — sets deleted: true, does not remove the node. ArchiveSupportCaseCommand only accepts a CLOSED case.
Arguments
| Argument | Type | Description | |
|---|---|---|---|
idpath | string | required |
Example call
A client sends this over the MCP session; Claude and other agents build it for you. The values are placeholders — the shape is real.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "delete_support_by_id",
"arguments": {
"id": "string"
}
}
}Result
There is no response body. On success the tool answers with one line of text saying so — DELETE /api/support/{id} succeeded., with the parameters filled in.
When it fails
A failed call returns isError: true with the API's message as text. A change the person declines, or lets time out, also comes back this way and nothing changes.
400The request was malformed or failed a guard.
403The caller is not platform staff.
404No support case with that id, or it is not CLOSED — the DAL's NOT_FOUND, carrying its sentence.
What the model is shown
This is the tool exactly as the server lists it in tools/list. The description starts with the REST call it makes.
{
"name": "delete_support_by_id",
"description": "DELETE /api/support/{id} — Platform-staff only (`requirePlatformStaff`). Backed by `Mutation.archiveSupportCase` — sets `deleted: true`, does not remove the node. `ArchiveSupportCaseCommand` only accepts a CLOSED case.\n\nThis changes data. The person is asked to confirm it before it runs, and nothing happens if they decline.",
"inputSchema": {
"type": "object",
"properties": {
"id": {
"type": "string"
}
},
"required": [
"id"
]
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true,
"openWorldHint": false
}
}