> 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/search-and-repurpose-episode-content/understand-content-generation-boundaries.md).

# Understand content-generation boundaries

Understand what the current Podigee agent surface can read, reuse, and verify.

The current MCP surface can read transcript segments, search spoken content, and inspect content assets that Podigee already generated.

## Supported agent work

* Read an episode transcript in pages.
* Search matching passages across a podcast or episode.
* List generated assets by source, type, or status.
* Read a generated asset's stored body and provenance.
* Use those sources to prepare a grounded draft in the client.

## Current boundary

The public tool catalog does not expose a general content-generation mutation. An agent can draft from retrieved context, but it must not claim that Podigee generated or saved a new asset unless a real operation and read-back prove that effect.

Missing transcript text, an unavailable asset body, or a failed generation status is not permission to invent output. Report the missing source and stop or narrow the task.

## Source fidelity

Keep direct quotes tied to transcript text and timestamps. Treat generated assets as drafts unless their editorial status and human review support reuse. Distinguish source facts from new proposed copy.

## Related tutorial

[Repurpose an episode with source-backed context](/documentation/start-here/ai-agents/search-and-repurpose-episode-content/repurpose-an-episode-with-source-backed-context.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/search-and-repurpose-episode-content/understand-content-generation-boundaries.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.