> 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/mcp-reference/pagination-filters-sorting-and-time-ranges.md).

# Pagination, filters, sorting, and time ranges

Shared pagination, episode filters, sort values, ISO 8601 dates, and valid range combinations.

## Pagination

List tools use `limit` and `offset`. The default limit is 25 and the maximum is 100 unless the tool schema declares a narrower rule. Negative offsets normalize to 0. Responses include `total`, `limit`, `offset`, and `next_offset` when another page exists.

Use the returned `next_offset`. Do not calculate continuation from the number of received items when filters or concurrent changes can affect the list.

## Episode filters

`list_episodes` supports title `query`, state `draft`, `scheduled`, or `published`, ISO 8601 `published_from` and `published_to`, and sort `newest`, `oldest`, or `title`.

The start of a date range must be before or equal to the end.

## Analytics ranges

Use exactly one range form:

* `from` and `to` together.
* `days_offset` from 1 to 366.
* Episode-only `days_since_published` from 1 to 366.

Do not combine range forms. Exact ranges cannot exceed 366 days. A bare ISO date starts at the beginning of that date in the application time zone. Use a date-time with an explicit offset when the instant matters.

## UTC and read-back

Compare the normalized returned timestamp with the intended local time before confirmation. After a schedule change, read the episode again and verify the stored instant.


---

# 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/mcp-reference/pagination-filters-sorting-and-time-ranges.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.