MCP toolsSearch and assistantsUpdated
Search traffic
What does mttr_traffic do?
Clicks from search, from Search Console. With a site: clicks by day, the totals against as many days before, and each page’s clicks now against before. Without one: every site, and searches none of them answers. A key may make this call on the sites it has claimed.
When to use it
- Before and after a change, to have a baseline.
- Traffic fell and you want to know which pages lost it.
What you ask
You say“How has search traffic to example.com moved?”
Your assistant calls
mttr_traffic({})| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | No | The site, as a domain such as example.com. |
show | One of these | No | lost (the default), gained, or all pages by clicks.lostgainedall |
limit | Number | No | How many to return. |
offset | Number | No | How many to skip, for the next part of a long list. |
What comes back
- Clicks by day, and totals against the days before.
- Each page now against before, those that lost most first.
- Only sites whose owner added mttr in Search Console have any.
41Mon
48Tue
52Wed
45Thu
39Fri
22Sat
26Sun
- Clicks
- 273241 before
- Impressions
- 9,8209,104 before
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/example.com/traffic, with your key as a bearer token:
curl "https://mttr.si/api/v1/sites/example.com/traffic" \
-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. |
| The key has not claimed the site | 404 | Claim it with mttr_claim, then mttr_claim_check. |
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_traffic in the API reference.