Skip to main content
Glama

ynab_list_months

Read-onlyIdempotent

List summary data for all budget months with pagination. Retrieve months newest-first, control page size and offset.

Instructions

List summary data for all budget months with pagination.

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: months[], total_count, returned_count, offset, has_more, next_offset, cached, cache_info

Examples:

  • List recent months: call with no args, months are newest-first

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

Errors:

  • "No default budget set" → run ynab_set_default_budget first

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
budget_idNo
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cachedNoIndicates if data was served from cache
monthsYesList of months
offsetYesOffset used for this response
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
Behavior4/5

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

Annotations already mark the tool as read-only and idempotent. The description adds valuable context such as pagination behavior, caching fields (cached, cache_info), and response structure 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?

Structured with clear sections (Args, Returns, Examples, Errors). Every sentence serves a purpose, no redundancy. Front-loaded with the core action.

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?

Covers pagination, error recovery, response fields, and examples. With an output schema present, the return field descriptions are sufficient. No gaps for correct tool invocation.

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 the description fully documents each parameter with types, defaults, and examples (e.g., limit default 50, response_format enum choices). This compensates completely for the schema's lack of descriptions.

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?

The description clearly states 'List summary data for all budget months with pagination', using a specific verb and resource. It distinguishes from sibling 'ynab_get_month' which retrieves a single month.

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?

Provides examples for common use cases and error handling (e.g., 'No default budget set' → run ynab_set_default_budget). However, it does not explicitly contrast with alternatives like ynab_get_month.

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