> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/list_follows.md).

# Twitter List Follows

Blocks for following and unfollowing Twitter/X lists.

## Twitter Follow List

### What it is

This block follows a specified Twitter list for the authenticated user.

### How it works

This block uses the Twitter API v2 via Tweepy to follow a Twitter List. Following a list adds it to your Lists tab and shows tweets from list members in your timeline when viewing that list.

The block authenticates using OAuth 2.0 with list write permissions and sends a POST request to add the follow relationship. Returns a success indicator confirming the list was followed.

### Inputs

| Input    | Description                  | Type | Required |
| -------- | ---------------------------- | ---- | -------- |
| list\_id | The ID of the List to follow | str  | Yes      |

### Outputs

| Output  | Description                           | Type |
| ------- | ------------------------------------- | ---- |
| error   | Error message if the operation failed | str  |
| success | Whether the follow was successful     | bool |

### Possible use case

**Curated Content Discovery**: Follow lists curated by industry experts to access filtered content streams.

**Topic Monitoring**: Follow lists focused on specific topics to stay informed without following individual accounts.

**Research Organization**: Follow competitor or industry lists to monitor activity without cluttering your main timeline.

***

## Twitter Unfollow List

### What it is

This block unfollows a specified Twitter list for the authenticated user.

### How it works

This block uses the Twitter API v2 via Tweepy to unfollow a Twitter List. The list is removed from your Lists tab but remains accessible if it's public.

The block authenticates using OAuth 2.0 with list write permissions and sends a DELETE request to remove the follow relationship. Returns a success indicator confirming the list was unfollowed.

### Inputs

| Input    | Description                    | Type | Required |
| -------- | ------------------------------ | ---- | -------- |
| list\_id | The ID of the List to unfollow | str  | Yes      |

### Outputs

| Output  | Description                           | Type |
| ------- | ------------------------------------- | ---- |
| error   | Error message if the operation failed | str  |
| success | Whether the unfollow was successful   | bool |

### Possible use case

**List Cleanup**: Unfollow lists that are no longer relevant or useful to your interests.

**Focus Management**: Reduce information overload by unfollowing less important lists.

**Account Organization**: Clean up your followed lists as part of regular account maintenance.

***


---

# 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://agpt.co/docs/integrations/block-integrations/list_follows.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.