List Property Values
vault_list_property_valuesLists distinct values for an Obsidian property key with occurrence counts, so you can see valid values before searching notes by that property.
Instructions
List distinct values for a specific property key with how often each occurs.
Example: vault_list_property_values({ key: "status" }) returns [{ value: "done", count: 211 }, { value: "active", count: 47 }, ...] Example: vault_list_property_values({ key: "tags", limit: 10 }) — the 10 most-used tags property values
When to use: Enumerating possible values for a property key before calling vault_search_by_property. Call vault_list_property_keys first to discover valid key names. A value listed here can be passed straight to vault_search_by_property, which matches text exactly and a complete number numerically too, so value "1" finds the number 1, the text "1", and a checked checkbox.
Parameters:
key is case-sensitive and must match exactly as returned by vault_list_property_keys.
folder names a whole folder, subfolders included: "Projects" covers "Projects/Archive" but not "ProjectsOld/", ignoring ASCII letter case.
limit keeps the most-used values; nothing in the response signals truncation; raise limit for more.
Behavior: Results can lag a file change by a few seconds.
Array elements (tags: ["a", "b"]) are counted individually, so the sum of counts may exceed the note count.
Each value is listed as text, and values with the same text share one row with combined occurrence counts: number 1 and text "1" count together, while text "1.0" stays separate.
Checkbox true and false come back as "1" and "0", counted with the numbers 1 and 0.
null values are skipped.
Errors:
An unknown key or empty folder returns an empty array, not an error.
"[SqliteError]: …" — the index failed, not the call; the message says what to do
Returns: JSON array of { value, count } sorted by count descending, then by value in binary text order ("10" before "2").
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"key": "<key>"
},
"name": "vault_list_property_values"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Property key name (e.g. "status", "type", "tags"). | |
| limit | No | Max values to return (default 50). | |
| folder | No | Restrict to a folder (e.g. "Projects") |