Get Audit Report
get_audit_reportRead saved performance causes, metrics, and page-metadata health. Use section:'pageMetadata' for the audited page's saved title, description, canonical and social-preview evidence. For fresh SEO, organic traffic or noindex questions, start with get_seo_evidence instead: it preserves source/scope and can inspect deployed HTML. Empty performance recommendations do not establish SEO health.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_audit_report"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| siteId | No | The site ID. Required only when auditId is omitted. | |
| auditId | No | Specific audit ID. It identifies the site, so siteId is optional when this is supplied. | |
| section | No | Defaults to 'summary': metrics with sources, finding, evidence, actions and limitations. Read focused evidence sections without running another audit; use 'full' only when needed. | summary |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tool | Yes | ||
| device | Yes | ||
| payload | Yes | Selected report section, or a truncated response with reason, availableSections and metricProvenance. Summary includes metrics, evidence, actions and limitations. | |
| identity | Yes | ||
| strategy | Yes | ||
| warnings | Yes | ||
| generatedAt | Yes | ||
| trustBoundary | Yes | ||
| auditCreatedAt | Yes | ||
| requestedDevice | Yes | ||
| metricProvenance | Yes |