# Log what you did (`mttr_log_work`)

Updated October 24, 2026.

## What does mttr_log_work do?

Tells mttr what was done on a site after each step: what was planned, changed or checked, where it got stuck, and the files and rules involved. It shows on your progress page. A key may make this call on the sites it has claimed.

Who may call it: Your claimed sites.

## When to use it

- After each step of work on a site.
- When the work is stuck and you want it on record.

## What you ask

You might say: “Log that you added sources to the drain guides.”

```
mttr_log_work({ site: "example.com", step: "planned", did: "did", found: "found", files: "files", rules: "rules", proposal: 10 })
```

| Argument | Type | Needed | What it is |
| --- | --- | --- | --- |
| `site` | Text | Yes | The site, as a domain such as example.com. |
| `step` | One of these: planned, changed, checked, stuck | Yes | Which step this was. |
| `did` | Text | Yes | What was done, in a sentence or two. |
| `found` | Text | No | What you found along the way, such as what was true of the site’s code. |
| `files` | Text | No | The files touched, separated by commas. |
| `rules` | Text | No | The mttr rules worked on, by id, separated by commas. |
| `proposal` | Number | No | The proposal this step carried out or checked, by its id from mttr_propose, when the site works by approval. |

## What comes back

- The entry, kept against the site.
- It shows on your progress page beside each read.

A sample, with made-up sites and figures:

| When | Step | What was done |
| --- | --- | --- |
| 10:42 | Changed | Added sources to 12 guides |
| 10:55 | Checked | Built the site, links resolve |
| 11:02 | Planned | Tap-to-call on service pages next |

## Over HTTP

```
curl -X POST "https://mttr.si/api/v1/account/notes" \
  -H "Authorization: Bearer $MTTR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"site":"example.com","step":"planned","did":"did","found":"found","files":"files","rules":"rules","proposal":10}'
```

## 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. |

## Sources

- [Model Context Protocol: tools](https://modelcontextprotocol.io/specification/2025-06-18/server/tools), Model Context Protocol: How an assistant calls a tool.

The call in full: [mttr_log_work in the API reference](https://mttr.si/docs/reference#mttr_log_work).

## Goes with

- [A link to your progress page](https://mttr.si/docs/tools/progress-link.md)
- [Your work board](https://mttr.si/docs/tools/todo.md)