MCP toolsWork and approvalsUpdated
Every proposal
What does mttr_proposals do?
Your proposals, newest first, each with where it stands, for one site or all of them. With a site, it also says whether that site is set to approve or automatic. A key may make this call on the sites it has claimed.
When to use it
- Before starting work on a site, to see how changes go out.
- To look back over what was asked and decided.
What you ask
You say“Show me the proposals for example.com.”
Your assistant calls
mttr_proposals({})| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | No | Only proposals for this site, and its mode. |
What comes back
- Each proposal with its rule, its pages and where it stands.
- With a site, whether it is set to approve or automatic.
| Proposal | Rule | Stands |
|---|---|---|
| p_7 | Show sources on guides | Approved |
| p_6 | Add a tap-to-call link | Declined |
| p_5 | Describe images | Expired |
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
It is GET /api/v1/account/proposals, with your key as a bearer token:
curl "https://mttr.si/api/v1/account/proposals" \
-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_proposals in the API reference.