> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/start-here/ai-agents/analyze-podcast-performance/find-available-analytics-reports.md).

# Find available analytics reports

List generated analytics reports available inside the connected Podigee account boundary.

Use the report list to discover generated files, not to replace live analytics summaries.

## Before you start

* Confirm the connected Podigee account.
* Know which podcast and reporting period you need.

## Find reports

1. Ask your agent to list analytics reports.
2. Review each report ID, podcast ID, formats, start date, end date, and creation time.
3. Match the report to the intended podcast and reporting period.
4. If `pagination.next_offset` is present, request the next page.
5. Keep the report metadata for the supported downstream access path.

The default page contains 25 reports. Only reports visible to the user and inside the connected tenant are returned.

## Expected result

You can identify whether a generated report exists for the intended podcast, period, and format.

## If no report matches

Use live analytics summary tools for current data. The MCP catalog lists report metadata but does not expose a report-generation or file-download tool.

## Next step

[Summarize podcast analytics](/documentation/start-here/ai-agents/analyze-podcast-performance/summarize-podcast-analytics.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/start-here/ai-agents/analyze-podcast-performance/find-available-analytics-reports.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.