Skip to main content
Glama

ynab_list_accounts

Read-onlyIdempotent

List all accounts from your YNAB budget with pagination. Supports optional budget ID, limit, offset, and returns account details in JSON or markdown format.

Instructions

List all accounts for a budget.

Args:

  • budget_id (string, optional): Budget UUID. Omit to use the default budget.

  • limit (int, optional): Max results per page. Default: 50.

  • offset (int, optional): Zero-based offset for pagination. Default: 0.

  • response_format (string, optional): "json" or "markdown" (default: "markdown").

Returns: accounts[], total_count, returned_count, offset, has_more, next_offset, cached, cache_info

Examples:

  • List all accounts (default budget): call with no args

  • Page 2: set limit=20, offset=20

Errors:

  • "No default budget set" → run ynab_set_default_budget first

  • "UNAUTHORIZED" → YNAB token expired

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
budget_idNo
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cachedNoIndicates if data was served from cache
offsetYesOffset used for this response
accountsYesList of accounts
has_moreYesWhether more items exist beyond this page
usedDeltaNoIndicates if delta merge optimization was applied for budgets
cache_infoNoHuman-readable cache status message (e.g., "Cache hit", "Cache miss")
next_offsetNoOffset for next page, if has_more is true
total_countYesTotal number of items available
returned_countYesNumber of items returned
Behavior5/5

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

Annotations already declare readonly, idempotent, non-destructive. The description adds behavioral details: pagination (limit, offset, has_more), caching info, and error conditions, going beyond annotations.

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?

Well-organized with Args, Returns, Examples, Errors sections. Purpose stated first. Every sentence adds value. Concise yet comprehensive.

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?

Given sibling tools, annotations, and presence of output schema (mentioned in description), the description covers return structure, pagination, caching, and errors adequately.

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

Parameters5/5

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

Schema coverage is 0%, but description compensates by documenting all 4 parameters with types, defaults, constraints, and examples (e.g., budget_id optional, limit exclusiveMin 0, offset min 0, response_format enum).

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

Purpose5/5

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

Clearly states 'List all accounts for a budget.' Verb and resource are specific, and it differentiates from siblings like ynab_get_account and ynab_list_budgets.

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

Usage Guidelines4/5

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

Includes error guidance (e.g., 'No default budget set' suggests ynab_set_default_budget) and examples for pagination. However, no explicit when-not-to-use compared to alternatives like ynab_get_account.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dizzlkheinz/ynab-mcpb'

If you have feedback or need assistance with the MCP directory API, please join our Discord server