MCP toolsInside a siteUpdated
One page
What does mttr_page do?
One page of a site: what it says about itself, the rules it fails with the fix for each, and the pages that link to it and that it links to. Any key may make this call, on any public site.
When to use it
- You are about to change one page.
- You want to know why a page fails.
What you ask
You say“Why does /guides/drain-cleaning fail on example.com?”
Your assistant calls
mttr_page({ site: "example.com", path: "/pricing" })
| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | Yes | The site, as a domain such as example.com. |
path | Text | Yes | The page, as a path such as /guides/gravel. |
What comes back
- Its title, description and headings.
- Each failing rule with its fix.
- Links in and links out.
- 1Show sources on guidesTrust1 page0.4 points
- 2Answer the first question right under itUnderstand1 page0.3 points
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}/page, with your key as a bearer token:
curl "https://mttr.si/api/v1/sites/example.com/page?path=%2Fpricing" \
-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_page in the API reference.