> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/web/dropdown/get-list-count.md).

# Get List Count

This is a pre-built Action located under the captured dropdown element. The functionality of this action in Avo Assure is to retrieve the total number of options available in the specified dropdown list. The result is stored in a dynamic variable for further use during test execution.

## **Syntax**

**Input Value**: `N/A`

| Argument | Description    |
| -------- | -------------- |
| N/A      | Not Applicable |

**Output Value**: `<Dynamic Variable>;<Dynamic Variable>(Optional)`

| Argument                                 | Description                                                                       |
| ---------------------------------------- | --------------------------------------------------------------------------------- |
| <p>\<Dynamic Variable><br>(Required)</p> | This dynamic variable stores the total count of values from the list or dropdown. |
| <p>\<Dynamic Variable><br>(Optional)</p> | This dynamic variable stores the status as **True** or **False**.                 |

### **Example: Retrieving the Total Number of Values in a List or Dropdown**

In this example, we explain how to get the total number of items available in a dropdown or list component.

* **Action:** Get List Count
* **Input Value:** N/A
  * This action does not require any value in the **Input Value** column. It automatically detects the captured list or dropdown element.
* **Output Value:** {List count}
  * The total number of items present in the list or dropdown (5) is stored in the **{List count}** dynamic variable.
  * If a second output variable is defined, it stores the action status with the following possible values:
    * **True:** If the list or dropdown count is retrieved successfully.
    * **False:** If the list or dropdown count is not retrieved successfully.
* **Logical Explanation:** The **Get List Count** action identifies the captured dropdown or list element and calculates how many items are available in it. The final count (5) is stored in the **{List count}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FwmP9v6jeIHXah8JJJ9Ck%2Fimage.png?alt=media&amp;token=d708334c-ac30-48e8-b145-f5698e1a848d" alt=""><figcaption></figcaption></figure>


---

# 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.avoautomation.com/avo-assure/actions/web/dropdown/get-list-count.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.