Skip to main content
Glama

ynab_list_payees

Read-onlyIdempotent

Retrieve payees from your YNAB budget with pagination controls. Get results in JSON or Markdown to manage transactions efficiently.

Instructions

List all payees for a budget 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: payees[], total_count, returned_count, offset, has_more, next_offset, cached, cache_info

Examples:

  • List all payees: call with no args

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

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
payeesYesList of payees
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds details about pagination behavior (has_more, next_offset) and caching (cached, cache_info). No contradictions with 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?

The description is well-structured with clear sections (Args, Returns, Examples, Errors). Every sentence adds value, no unnecessary words.

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 the output schema exists, the description still provides return field names and usage examples. It covers error handling and pagination thoroughly, leaving no gaps.

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?

All four parameters are fully described with types, optionality, defaults, and formats (e.g., budget_id as UUID, limit with max, offset zero-based, response_format enum). This compensates for 0% schema coverage.

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 explicitly states 'List all payees for a budget with pagination', providing a specific verb and resource. It distinguishes from sibling tools like ynab_list_accounts by clearly focusing on payees.

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?

The description includes usage guidance such as optional parameters with defaults, pagination examples, and an error case ('No default budget set'). It does not explicitly state when not to use, but the context is clear enough.

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