> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/command-line-interface/reference/publisher/collections-items-list.md).

# collections items list

List items in a collection

## Synopsis

```shell
omics publisher collections items list
  --collection=COLLECTION_ID
  [--limit=NUMBER]
  [--type=ITEM_TYPE]
  [--max-results=NUMBER]
```

## Description

List all items in a collection. Items represent the files, tables, or other data objects that are part of the collection.

## Examples

List all items in a collection.

```shell
omics publisher collections items list --collection my-collection
```

List only a specific type of items.

```shell
omics publisher collections items list --collection my-collection --type file
```

Limit the number of results returned.

```shell
omics publisher collections items list --collection my-collection --max-results 100
```

## Flags

### `--collection`=`COLLECTION_ID`

The ID or slug name of the collection to list items from.

### `--limit`=`NUMBER`

Set the page size returned by the server. Defaults to 50.

### `--type`=`ITEM_TYPE`

Filter items by type. Use this to list only specific types of items in the collection.

### `--max-results`=`NUMBER`

Limit the maximum number of results printed to the console.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.omics.ai/products/command-line-interface/reference/publisher/collections-items-list.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.