MCP toolsRivals and marketsUpdated
Content gaps
What does mttr_gaps do?
Subjects a site’s rivals write about that nothing on the site comes close to in meaning, the one most rivals cover first. A key may make this call on the sites it has claimed.
When to use it
- You plan what to write next.
What you ask
You say“What do rivals write about that example.com does not?”
Your assistant calls
mttr_gaps({ site: "example.com" })
| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | Yes | The site, as a domain such as example.com. |
limit | Number | No | How many to return. |
What comes back
- Each missing subject with the rival pages on it.
- The nearest page on the site, so you can tell how far off it is.
| Subject | Rivals covering it | Nearest page here |
|---|---|---|
| Tankless water heaters | 5 | /services/water-heaters |
| Root intrusion | 3 | /guides/drain-cleaning |
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}/gaps, with your key as a bearer token:
curl "https://mttr.si/api/v1/sites/example.com/gaps" \
-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_gaps in the API reference.