MCP toolsWork and approvalsUpdated
The next page to write
What does mttr_content_next do?
The brief for the page most worth writing next on a site you claimed: the question, why it is worth a page, the kind of page and its address, the facts to use, the voice, and the rules it will be held to. mttr does not write the page. At most three briefs are open at once. A key may make this call on the sites it has claimed.
When to use it
- You want to know what page to write next.
- A page from the last brief is live and read.
What you ask
You say“What page should I write next for my site?”
mttr_content_next({ site: "example.com" })
| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | Yes | The site, as a domain such as example.com. |
What comes back
- One brief, kept so it is handed out once, with the words to work from.
- The briefs still open, or why there is nothing to brief yet.
| Write | Why | At |
|---|---|---|
| How much does a French drain cost? | Searched 120 times, no page close | /french-drain-cost |
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/next, with your key as a bearer token:
curl -X POST "https://mttr.si/api/v1/account/content/next" \
-H "Authorization: Bearer $MTTR_KEY" \
-H "Content-Type: application/json" \
-d '{"site":"example.com"}'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_next in the API reference.