YNAB MCP Server

List accounts

list_accounts

Read-only

Fetch a budget plan's accounts and balances, including each account's transfer payee ID, so you can initiate transfers or review account data with pagination and optional closed accounts.

Instructions

List the plan's accounts with their balances.

Each account includes its transfer_payee_id: use it as the payee of a transaction to transfer money into that account.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of accounts to return per page (default: 100)
`offset`	No	Number of accounts to skip for pagination (default: 0)
`include_closed`	No	Whether to include closed accounts (default: false)

Output Schema

Name	Required	Description	Default
`accounts`	Yes	List of accounts
`pagination`	Yes	Pagination information

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 26, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish read-only and closed-world behavior, and the description adds useful context that accounts include balances and transfer_payee_id. It does not discuss pagination or whether closed accounts are included by default, but those details are covered by the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no wasted wording. The core action and resource are front-loaded, followed immediately by the most useful field-level context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only listing tool with fully described parameters, annotations, and an output schema, the description provides enough context to select and invoke it correctly. The transfer_payee_id note adds practical orientation without needing to repeat schema or output details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so limit, offset, and include_closed are already fully documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, making 3 the appropriate baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the specific action (list) and resource (the plan's accounts), and adds that balances are included. It does not explicitly differentiate from sibling tools such as create_account or list_payees, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains a practical follow-up use for transfer_payee_id when transferring money into an account, but it does not state when to choose list_accounts over related siblings or when not to use it. Usage is implied rather than explicitly guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.