What changed in AI visibility
get_changesCompare a website's AI-visibility scores between two snapshots that asked the same question to show overall and per-engine changes, or explain why no comparable change exists.
Instructions
Report what changed in a website's AI-visibility score, only between two snapshots that asked the same question. Use this when someone asks "did anything change," "what's different this week/month," or "did my AI visibility drop." The domain need not be tracked: history accrues from any audit of it, tracked or not — track_site adds the weekly re-audits to the series, it is not a precondition, so do not track a site just to answer a change question. Returns the change in the overall score and the per-engine score changes, for engines measured both times — the overall only when the same engines answered both snapshots, otherwise it is null with an overall_note naming which answered each, and the per-engine changes stand alone; a summary says the change in plain sentences; competitor_changes, new_issues and resolved_issues are always empty, since snapshots record neither competitors nor audit issues. A change is only ever measured between two snapshots that asked the same question (the same business name, market and queries); when there is no such pair it says why instead of giving a number, with the date the series re-baselined when it did. The series is the measured weekly re-audits and any audit that asked the same question as the newest recorded one, while it has no gap longer than four weeks and a day from the newest weekly re-audit that recorded its question, through each later snapshot of the series (weekly re-audits included, recorded or not), to the newest measured snapshot; otherwise every measured snapshot. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"domain": "<domain>"
},
"name": "get_changes"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | Optional ISO date or "last_check". | |
| domain | Yes | The website domain, e.g. "example.com". |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | Present when skipped_snapshots is above 0, when the two snapshots compared were answered by different engines, when newer measured snapshots were left out of the series, or when newer weekly re-audits measured nothing of the business: which, and why, in words. Relay it. | |
| summary | No | The change in plain sentences, built from this result's two snapshots and any newer run the comparison leaves out: the overall scores and move, each assistant that moved, those newer runs, and what Pro checks each week; note beside it carries any snapshot passed over in between. | |
| new_issues | Yes | Always empty: AI-visibility snapshots record no audit issues. Kept for clients that read it. | |
| score_delta | Yes | Only ever between two snapshots that asked the same question AND were answered by the same engines. When there is no such pair, including a re-baseline after the business name, market or queries changed, the tool returns NOT_YET_AVAILABLE saying so, never a number; when the pair exists but different engines answered the two snapshots, the overall is not subtracted and is null with overall_note, and engine_changes still compares every engine that answered both. | |
| overall_note | No | Present exactly when score_delta is null: the two snapshots were answered by different engines, and which answered each. Relay it — a null delta for this reason must not read like a null for want of history. | |
| engine_changes | Yes | ||
| to_captured_at | No | When the later one was. | |
| resolved_issues | Yes | Always empty: AI-visibility snapshots record no audit issues. Kept for clients that read it. | |
| from_captured_at | No | When the earlier snapshot compared was captured. | |
| skipped_snapshots | No | Snapshots passed over because they asked a different question (another business name, market or queries) or do not record what they asked. | |
| competitor_changes | Yes | Always empty: AI-visibility snapshots record no competitors. Kept for clients that read it. |