MCP toolsInside a siteUpdated
How a site is put together
What does mttr_structure do?
A site’s sections, how many clicks each sits from the home page, how much of each is linked from page content, and the links between sections. Any key may make this call, on any public site.
When to use it
- Deep pages are hard to reach and you want to see where.
- You plan to rework a site’s menus or hubs.
What you ask
You say“How is example.com put together?”
Your assistant calls
mttr_structure({ site: "example.com" })
| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | Yes | The site, as a domain such as example.com. |
links | One of these | No | Which links to count between sections. Content links when left out.contentall |
What comes back
- Each section with its pages and clicks from home.
- How much of it is linked from content.
- The links between sections.
| Section | Pages | Clicks from home | Linked in content |
|---|---|---|---|
| /guides | 42 | 2 | 64% |
| /services | 18 | 1 | 89% |
| /towns | 30 | 3 | 12% |
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}/structure, with your key as a bearer token:
curl "https://mttr.si/api/v1/sites/example.com/structure" \
-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_structure in the API reference.