list_budgetsLists all YNAB budgets and their IDs so you can identify the default budget or pass a budgetId to other tools.
List budgets and IDs. Omit budgetId in other tools for the default budget.
| Name | Required | Description | Default |
|---|---|---|---|
| includeAccounts | No | If true, include each budget's account list in the response |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v6.1.0Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"v5.4.0Output schema / properties / result / descriptionRemoved value: -"Structured result returned by List Budgets."v5.1.1Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / properties / includeAccountsAdded value: +{
+ "description": "If true, include each budget's account list in the response",
+ "type": "boolean"
+}Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "result": {
+ "description": "Structured result returned by List Budgets."
+ }
+ },
+ "required": [
+ "result"
+ ],
+ "type": "object"
+}v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this a read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds a useful cross-tool usage note but says nothing about response shape, ordering, or what happens with the default budget flag.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two terse sentences with zero filler; the core action comes first and the usage tip follows immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, and the annotations carry the safety profile. For a one-optional-parameter list tool this is nearly complete, missing only explicit guidance on when to prefer listing versus fetching a single budget.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single includeAccounts flag is fully documented there. The description adds no parameter-level detail, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List budgets and IDs'), which clearly distinguishes this from the singular get_budget sibling. However, it does not explicitly say how it differs from get_budget or get_budget_settings beyond the plural naming.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The second sentence gives concrete cross-tool guidance: omit budgetId elsewhere to target the default budget, which implies this tool is the discovery step for budget IDs. It stops short of explicitly stating 'call this first' or naming alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.