# list_findings

Read only. List the findings from the latest analysis of an asset (what is happening and why).

## When to use it

- Use it when: You need what is happening on the site and why, from the latest analysis.
- Not when: You need a number; findings carry severity and impact, not scores.

## Parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| assetId | string | yes | The Visibility Asset UUID to query. |
| severity | string | no | Only findings with this severity, as stored (for example critical). |
| limit | number | no | Maximum items to return; default 100, at most 500. |

## What comes back

| Field | Meaning |
| --- | --- |
| assetId | The asset asked about, echoed back. |
| dataStatus | One of ok, not_measured or empty_filter. not_measured means no measurement of this kind exists yet, which is not zero; empty_filter means data exists and your filter matched none of it. |
| href | The dashboard page that holds the evidence behind this result, for the right site. A signed-in person can open it; quote it beside the numbers. |
| collectedAt | When the snapshot these values come from was collected. Absent when there is no snapshot. |
| findings | Each with title, severity, impact, detail, provenance and confidence. Empty with dataStatus ok means the analysis found nothing to report. |
| total | How many findings the analysis holds before the severity filter and the limit. |

## What comes back with the number

Shares arrive with the sample size behind them and a 95% Wilson interval. Values carry a provenance of measured, estimated or derived. A pillar that was not measured reports as not measured rather than as zero, and the composite Visibility Score is held until at least 5 of its 7 pillars are measured.

## Example request

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_findings",
    "arguments": {
      "assetId": "<assetId from list_assets>",
      "severity": "<severity>",
      "limit": "<number>"
    }
  }
}
```

## dataStatus

- `ok`: There is at least one result, or a measured zero.
- `not_measured`: No measurement of this kind exists yet for the asset. Not zero, and not a broken connection.
- `empty_filter`: Data exists, and the filter you passed matched none of it. Retry without the filter.

## Example prompt

> Call list_findings for my site with severity critical and group them, keeping each finding's provenance.

## Calling it

Connect the MCP server at `https://app.seoaio.ai/api/mcp` over the Streamable HTTP transport. Per-customer
authentication is required, so nothing is exposed without it. Call `list_assets` first:
every other tool needs an `assetId` from it. A proposal is approved or rejected by a
person at `https://app.seoaio.ai/dashboard/requests`.

## Next

- [list_recommendations](https://seoaio.ai/docs/tools/list_recommendations/md)
- [propose_measurement](https://seoaio.ai/docs/tools/propose_measurement/md)

## More

- The skill, which carries the call order and the rules for quoting a number: https://seoaio.ai/SKILL.md
- Troubleshooting: https://seoaio.ai/docs/troubleshooting
- This page as HTML: https://seoaio.ai/docs/tools/list_findings