List Property Values
vault_list_property_valuesDiscover a property's distinct values with note counts before filtering. Unpacks array properties and sorts by frequency to reveal the most common values.
Instructions
List distinct values for a specific property key with note counts. Useful for discovering the range of values a property takes before searching.
Example: vault_list_property_values({ key: "status" }) returns [{ value: "active", count: 47 }, { value: "done", count: 211 }, ...]
When to use: Enumerating possible values for a property key before calling vault_search_by_property. Handles both scalar properties (status: "active") and array properties (tags: ["a", "b"]) — array elements are unpacked and counted individually, so the sum of counts may exceed the note count. An unknown key or empty folder returns an empty array, not an error. Call vault_list_property_keys first to discover valid key names.
Parameters:
key is case-sensitive and must match exactly as returned by vault_list_property_keys. Values are always strings — numeric and boolean properties are stringified for counting.
folder + key interact: folder restricts counting to a subtree, so the same key can return different value distributions depending on folder scope.
limit (default 50) applies after sorting by count descending, so you always get the most-used values first. Increase for high-cardinality keys like "title" or "created".
Returns: JSON array of { value, count } sorted by count descending.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Property key name — use vault_list_property_keys to discover valid keys (e.g. "status", "type", "tags"). | |
| limit | No | Max values to return (default 50). Increase for high-cardinality properties. | |
| folder | No | Restrict to a folder prefix (e.g. "Projects") |