MCP toolsRead and fixUpdated
Where a read stands
What does mttr_job do?
How a read asked for stands: waiting, running, done or failed, and how many reads are ahead of it. A key may make this call on the sites it has claimed.
When to use it
- You asked for a read and are waiting on it.
What you ask
You say“Is the read of example.com done yet?”
Your assistant calls
mttr_job({ id: 4242 })
| Argument | Type | Needed | What it is |
|---|---|---|---|
id | Number | Yes | The job id that mttr_rescan returned. |
What comes back
- Its state, and how many reads are ahead of it.
- Why it failed, when it did.
- Waiting
- 2Running
- 3Done
Running. 64 of 100 pages read.
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
It is GET /api/v1/jobs/{id}, with your key as a bearer token:
curl "https://mttr.si/api/v1/jobs/4242" \
-H "Authorization: Bearer $MTTR_KEY"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_job in the API reference.