# One page (`mttr_page`)

Updated October 24, 2026.

## 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.

Who may call it: Any key.

## When to use it

- You are about to change one page.
- You want to know why a page fails.

## What you ask

You might say: “Why does /guides/drain-cleaning fail on example.com?”

```
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.

A sample, with made-up sites and figures:

1. Show sources on guides (Trust), 1 page, worth 0.4 points
2. Answer the first question right under it (Understand), 1 page, worth 0.3 points

## Over HTTP

```
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`. |

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

## Goes with

- [Pages](https://mttr.si/docs/tools/pages.md)
- [Worked examples](https://mttr.si/docs/tools/examples.md)