List Entries
list_entriesRetrieve content entries from a collection with filtering, sorting, and pagination options to manage structured data efficiently.
Instructions
List content entries for a collection with advanced filtering, sorting, and pagination. Use the 'where' parameter for powerful queries. Read the 'query-reference' resource for full documentation on operators and examples.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| collection_slug | Yes | The collection slug | |
| where | No | Filter conditions as a nested object. Supports operators: eq, lt, lte, gt, gte, not, like, in, not_in, null, not_null, between, not_between. Simple: { "status": "published" }. With operators: { "price": { "lt": 50 }, "title": { "like": "news" } }. OR group: { "or": [{ "tags": "clearance" }, { "campaign": { "name": "Summer" } }] }. Relation filter: { "author": { "name": { "eq": "John" } } }. Core columns (id, uuid, locale, status, created_at, updated_at, published_at) can be filtered directly. | |
| locale | No | Filter by locale (e.g. 'en') | |
| state | No | Filter by state: 'only_draft' or 'with_draft'. Defaults to published entries only. | |
| sort | No | Sort by field:direction, comma-separated for multiple. Examples: 'created_at:desc', 'title:asc,created_at:desc'. Supports core columns (id, created_at, updated_at, published_at) and custom field names. | |
| paginate | No | Enable pagination with N items per page. Returns paginated response with meta data. Overrides limit/offset. | |
| limit | No | Limit the number of results (ignored if paginate is set) | |
| offset | No | Skip N results (requires limit to be set) | |
| first | No | If true, return only the first matching entry as a single object instead of an array | |
| count | No | If true, return only the count of matching entries: { count: N } | |
| exclude | No | Comma-separated field names to exclude from response (e.g. 'content,excerpt') |