MCP toolsWork and approvalsUpdated
Mark a task done
What does mttr_queue_done do?
Says a queued task is done. The fix itself counts only once a later read finds it passing, so ask for a fresh read after. A key may make this call on the sites it has claimed.
When to use it
- You have finished a task from the queue.
What you ask
You say“I finished the sources task. Mark it done and read the site again.”
Your assistant calls
mttr_queue_done({ id: 4242 })
| Argument | Type | Needed | What it is |
|---|---|---|---|
id | Number | Yes | The task id from mttr_queue. |
What comes back
- The task taken off the queue.
- A reminder that the fix counts once a read finds it passing.
- Queued
- Worked on
- 3Marked done
- 4Checked by a read
Task t_41 is done. Read the site again to count the fix.
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
It is POST /api/v1/account/queue/done, with your key as a bearer token:
curl -X POST "https://mttr.si/api/v1/account/queue/done" \
-H "Authorization: Bearer $MTTR_KEY" \
-H "Content-Type: application/json" \
-d '{"id":4242}'When it fails
| When | Status | What to do |
|---|---|---|
| Your assistant has no key yet | 401 over MCP | Sign up with mttr_signup, then connect again with the key it gives. |
Every error’s wording is in the API reference.
The call in full, with its HTTP address, each argument’s type, who may make it and the call in four languages, is mttr_queue_done in the API reference.