# Posts about a new page (`mttr_content_posts`)

Updated October 24, 2026.

## What does mttr_content_posts do?

For a page that went live from one of your briefs, a brief for an X post and one for LinkedIn: the point, one fact of your own that carries it, the link, your voice and the room left. You or your assistant write them; mttr writes no post and posts nothing. A key may make this call on the sites it has claimed.

Who may call it: Your claimed sites.

## When to use it

- A page from a brief is live and you want people to see it.

## What you ask

You might say: “Give me post briefs for the French drain page we just put live.”

```
mttr_content_posts({ site: "example.com", brief: 10 })
```

| 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. Its page must be live. |

## What comes back

- Two post briefs, X and LinkedIn, and the words to write from.

A sample, with made-up sites and figures:

| For | The fact that carries it | Room |
| --- | --- | --- |
| X | Serves Cicero and Liverpool | 256 characters |
| LinkedIn | Founded in 1998 | 2,960 characters |

## Over HTTP

```
curl "https://mttr.si/api/v1/account/content/posts?site=example.com&brief=10" \
  -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. |

## 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_content_posts in the API reference](https://mttr.si/docs/reference#mttr_content_posts).

## Goes with

- [Say where a page went](https://mttr.si/docs/tools/content-done.md)
- [The next page to write](https://mttr.si/docs/tools/content-next.md)