MCP toolsWork and approvalsUpdated
Say where a page went
What does mttr_content_done do?
Tells mttr where the page for one of your briefs went on your site. The brief goes live when the next read finds that page, and keeps your score and place from then beside where you were when it was handed out. A key may make this call on the sites it has claimed.
When to use it
- You or your assistant published the page from a brief at an address of your own choosing.
What you ask
You say“I put the sump pump page at /services/sump-pumps. Tell mttr and read the site again.”
mttr_content_done({ site: "example.com", brief: 10, path: "/pricing" })
| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | Yes | The site, as a domain such as example.com. |
brief | Number | Yes | The brief's id, from mttr_content_next. |
path | Text | Yes | The page's path on the site, starting with /, such as /services/sump-pumps. |
What comes back
- The brief, waiting for a read to find its page.
- Handed out
- 2Written
- 3Found by a read
- 4Live
Brief 12 waits for a read at /services/sump-pumps.
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/content/done, with your key as a bearer token:
curl -X POST "https://mttr.si/api/v1/account/content/done" \
-H "Authorization: Bearer $MTTR_KEY" \
-H "Content-Type: application/json" \
-d '{"site":"example.com","brief":10,"path":"/pricing"}'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_content_done in the API reference.