MCP toolsRulebook and crawlUpdated
The crawl
What does mttr_crawls do?
The crawl as it stands: the sites being read now, the next in line, and how the reads that ended over the last 1, 7 or 30 days ended. Only whoever runs this mttr may make this call.
When to use it
- You run mttr and want to see how the crawl is going.
What you ask
You say“How is the crawl going?”
Your assistant calls
mttr_crawls({})| Argument | Type | Needed | What it is |
|---|---|---|---|
days | Number | No | The range, in days: 1, 7 or 30. The week when left out or anything else. |
What comes back
- Sites being read now and next in line.
- How recent reads ended, by count.
| Ended as | Last day | Last 7 days |
|---|---|---|
| Read | 412 | 2,904 |
| Closed to crawlers | 31 | 198 |
| Failed | 6 | 44 |
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
It is GET /api/v1/crawls, with your key as a bearer token:
curl "https://mttr.si/api/v1/crawls" \
-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. |
| The key is a person’s, not the owner’s | 403 | Nothing: only whoever runs mttr makes this call. |
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_crawls in the API reference.