Skip to main content
Glama

ynab_list_months

Read-onlyIdempotent

List budget month summaries with pagination. Retrieve monthly data for your YNAB budget, controlling 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
budget_idNo
limitNo
offsetNo
response_formatNomarkdown

Output Schema

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

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

Beyond annotations (readOnly, idempotent), the description discloses pagination details (limit, offset, next_offset, has_more), caching (cached, cache_info), default ordering (newest-first), and error conditions. This adds useful behavioral context.

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

Conciseness4/5

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

The description is well-structured with a summary, parameter list, returns, examples, and errors. It is front-loaded with the purpose. While slightly verbose, each section is meaningful and no redundant information is present.

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

Completeness4/5

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

Given the tool's simplicity and the presence of an output schema, the description covers parameters, returns, pagination, caching, and common errors. It provides examples for typical use. Could be extended with a note about the summary nature of the data, but overall complete.

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?

Despite 0% schema description coverage, the description fully documents each parameter with type, defaults, and usage (e.g., budget_id: omit for default, limit: max results per page). Examples further clarify usage, fully compensating for the missing schema 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 it lists summary data for all budget months with pagination. It uses specific verb and resource (list months) and distinguishes from sibling list tools like ynab_list_accounts 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 Guidelines3/5

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

Usage guidelines are implied through error handling (e.g., 'No default budget set' suggests a prerequisite) but there is no explicit when-to-use or alternative tools. The description does not mention, for example, using ynab_get_month for a specific month instead.

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