mbx_ack
Acknowledge mbx messages
Mark messages as dealt with (optionally with a short note). Acked messages leave the unread inbox. Ack after you reply or act; no need to send a separate “acknowledged” message. Keep did to one line of at most 200 characters, action first; put detail in your thread reply. Next: mbx_inbox for anything else.
Annotations
Section titled “Annotations”| Field | Value |
|---|---|
idempotentHint |
true |
execution.taskSupport |
"forbidden" |
| Parameter | Type | Required | Default | Constraints | Description |
|---|---|---|---|---|---|
ids |
string[] |
yes | 1–50 items; each: length ≥ 6 | ||
note |
string |
no | length ≤ 500 | ||
did |
string |
no | length ≤ 10000 | if you acted on the request: one line, at most 200 characters, saying what you did, action first (owner’s audit log; longer text is cut and marked truncated) |
Input JSON schema
Section titled “Input JSON schema”{ "$schema": "http://json-schema.org/draft-07/schema#", "type": "object", "properties": { "ids": { "minItems": 1, "maxItems": 50, "type": "array", "items": { "type": "string", "minLength": 6 } }, "note": { "type": "string", "maxLength": 500 }, "did": { "description": "if you acted on the request: one line, at most 200 characters, saying what you did, action first (owner's audit log; longer text is cut and marked truncated)", "type": "string", "maxLength": 10000 } }, "required": [ "ids" ]}