> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/cookbook/clarity/data-utility/filter-items-from-a-list.md).

# Filter items from a list

{% code fullWidth="false" expandable="true" %}

```clarity
(define-read-only (filter-item (l (list 100 uint)) (remove uint))
  (get newList (fold remove-value l { compareTo: remove, newList: (list) }))
)

(define-private (remove-value (listValue uint) (trackerTuple { compareTo: uint, newList: (list 100 uint) }))
  (merge trackerTuple {newList:
    (if (is-eq listValue (get compareTo trackerTuple))
      (get newList trackerTuple)
      (unwrap-panic (as-max-len? (append (get newList trackerTuple) listValue) u100))
    )
  })
)

;; Example usage
(filter-item (list u1 u2 u3 u2 u4) u2) ;; Returns (u1 u3 u4)
```

{% endcode %}

### Description

Remove specific items from lists using fold in Clarity

### Use Cases

* Removing blacklisted addresses from access lists
* Filtering out completed tasks from todo lists
* Excluding specific tokens from portfolios
* Data cleanup in smart contracts

### Key Concepts

* **Accumulator** - Tracks the value to remove and builds the new list
* **Conditional append** - Only adds items that don't match the filter
* **Type safety** - Maintains list type and maximum length
* This pattern uses `fold` to iterate through a list and build a new list


---

# 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.stacks.co/cookbook/clarity/data-utility/filter-items-from-a-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.