> 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/manage-episodes/inspect-an-episode.md).

# Inspect an episode

Read one episode's metadata, media, publication, transcript, and distribution context.

Read the full episode detail before you update, publish, or delete it.

## Before you start

* Find the episode inside the intended podcast.
* Keep its numeric episode ID.

## Inspect the episode

1. Ask your agent to get the episode by ID.
2. Confirm the episode ID and podcast ID.
3. Review title, subtitle, description, show notes, authors, number, season, and episode type.
4. Review `published_at` and determine whether the episode is a draft, scheduled, or published.
5. Review `has_media`, `production_id`, duration, and media-related settings.
6. Review the permalink, external URL, cover image, labels, and keywords.
7. Review all chapter marks.
8. Review transcript availability, segment count, and update time.
9. Keep the read-back before any mutation.

Transcript detail is paginated separately. The episode detail reports whether transcript segments are available, not the complete transcript text.

## Expected result

You can identify the exact episode, its current publication state, and the fields affected by the next action.

## If the episode cannot be read

Confirm the episode ID, connected account, and podcast access. Do not use an episode ID from another tenant.

## Next step

* [Update episode metadata](/documentation/start-here/ai-agents/manage-episodes/update-episode-metadata.md)
* [Change an episode publication state](/documentation/start-here/ai-agents/manage-episodes/change-an-episode-publication-state.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/manage-episodes/inspect-an-episode.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.