Opengraph io MCP

listSiteAudits

Read-onlyIdempotent

Retrieve past site audits for your organization to track domain scores over time, filter by status or date, and obtain audit IDs for detailed reports.

Instructions

List past site audits for the connected organization — newest first by default. Use this to find an audit to inspect, to track a domain's score over time, or to get the previous audit ID for a comparison.

Filter with q (domain substring), status, from / to (ISO dates), or websiteId to see every run for one monitored site. Page with limit and offset.

Returns audit IDs — feed one to getSiteAuditReport for full results, or to getSiteAuditChanges to see what moved since the previous run.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Filter by domain substring.
`to`	No	Only audits created on or before this ISO date.
`from`	No	Only audits created on or after this ISO date.
`sort`	No	Server-supported sort key, e.g. '-createdAt'.
`limit`	No	How many audits to return (1–100). Defaults to the server's page size.
`offset`	No	Rows to skip, for paging.
`status`	No	Only return audits in these states.
`websiteId`	No	Only audits for this monitored website — use it to build a single site's history.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`total`	Yes
`audits`	Yes
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.1.0Sep 22, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, and non-destructive. The description adds behavior not in annotations: newest-first default, filtering/paging semantics, and that it returns audit IDs for downstream tools. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact paragraphs, each purposeful: purpose and use cases, filtering/paging, and return value/next steps. No filler; front-loads the most important fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no required params, rich annotations, and an output schema, the description covers what the tool returns, how to filter/page, and how to continue to getSiteAuditReport/getSiteAuditChanges. Nothing essential is missing for an agent to select and invoke it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 8 params at 100%, so baseline is 3, but the description adds use-case semantics: websiteId builds a single site's history, from/to are ISO dates, and limit/offset page. It does not explain sort, but the default sort is stated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List past site audits') plus scoping ('for the connected organization') and default ordering. It also names downstream tools, distinguishing it from getSiteAuditReport/getSiteAuditChanges and from mutation siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use it: to find an audit to inspect, track scores over time, or get previous audit ID for comparison. It does not spell out exclusions versus startSiteAudit/deleteSiteAudit, but the purpose and filter guidance make context clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.