> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iqrush.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Compare brand visibility

> Compare brands under the same measured conditions.

Answer: “How often are we mentioned compared with the brands measured in this project, and does the pattern differ by platform?”

## Prepare the scope

Use `list_projects` and `list_runs` to choose the project and completed run. Check readiness, then call `get_results_stability` for the same run and supported filters. For each measurement, preserve the scope, returned confidence interval, and row-quality fields. See [run selection](/developers/guides/07-projects-and-runs) and [decision-grade measurement](/developers/guides/10-stability).

The JSON examples below are MCP `tools/call` parameter objects. Replace ID placeholders and sample selections with values discovered in your account.

## Retrieve the evidence

1. Call `get_project` to read the configured brand terms and competitor context.
2. Request entity-level mention coverage for the configured brand and competitors, grouped by platform.
3. Use `list_mention_statements` for selected brands to inspect the supporting answers. Follow the returned cursor for more statements.

```json theme={null}
{
  "name": "get_mention_score",
  "arguments": {
    "project_id": "PROJECT_ID",
    "run_id": "RUN_ID",
    "metric": "coverage",
    "aggregation_level": "entity",
    "subject": {
      "kind": "self_and_competitors"
    },
    "group_by": [
      "platform"
    ]
  }
}
```

## Build the report

Create one row per brand entity and platform, retaining `data.rows[].entity_or_bundle`, `group_by_values`, and `estimate`. Display coverage with the returned interval and a note for limited rows. Follow with a small set of supporting statements and their sources.

Do not add alias coverage percentages together. A response can mention several aliases, and this request reports entities. Use [response handling](/developers/guides/09-responses-and-metrics) to keep entity rows separate from headline brand-term coverage.

For change over time, use comparable runs and the [comparison guide](/developers/guides/11-compare-measurements). The paired contrast tool in this edition does not test mention coverage, so this recipe does not promise that significance test.

Reference: [mention scores](/developers/tools/get_mention_score), [statements](/developers/tools/list_mention_statements).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.