MCP toolsInside a siteUpdated
Topics
What does mttr_topics do?
What a site covers: its subjects and the pages under each, pages competing for the same search, and places a subject is missing from. Any key may make this call, on any public site.
When to use it
- You plan new pages and want to know what is covered.
- Two pages may be competing for one search.
What you ask
You say“What does example.com cover, and what competes?”
Your assistant calls
mttr_topics({ site: "example.com" })
| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | Yes | The site, as a domain such as example.com. |
What comes back
- Each subject with its pages.
- Pages competing for one search.
- Subject names come from a model and are marked as quoted.
| Subject | Pages | Note |
|---|---|---|
| Drain cleaning | 9 | Two pages compete |
| Septic care | 6 | |
| Water heaters | 1 | Missing from /towns |
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
It is GET /api/v1/sites/{site}/topics, with your key as a bearer token:
curl "https://mttr.si/api/v1/sites/example.com/topics" \
-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. |
| mttr has no public report of the site yet | 404 | Ask for a read with mttr_rescan, then watch it with mttr_job. |
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_topics in the API reference.