Skip to main content
Glama

ynab_update_category

Idempotent

Set a new budgeted amount for a YNAB category in the current month. Provide funding in decimal currency or milliunits, and optionally preview with a dry run before saving.

Instructions

Update the budgeted amount for a category in the current month.

Args:

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

  • category_id (string, required): Category UUID.

  • budgeted_decimal (number, preferred): New funding amount in decimal currency units.

  • budgeted_milliunits (int, alternative): Explicit raw YNAB milliunits.

  • budgeted (int, deprecated): Backward-compatible alias for budgeted_milliunits.

  • dry_run (boolean, optional): Preview without saving. Default: false.

Returns: updated category with new budgeted, activity, balance.

Examples:

  • Budget $100: set budgeted_decimal=100.00

  • Already-converted data: set budgeted_milliunits=100000

  • Dry run: set dry_run=true

Errors:

  • "No default budget set" → run ynab_set_default_budget first

Write safety: call without confirmation_token to preview. Execute the identical validated request with the short-lived confirmation_token returned by that preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNo
budgetedNoDeprecated legacy alias for budgeted_milliunits. Use budgeted_decimal or budgeted_milliunits.
budget_idNo
category_idYes
budgeted_decimalNoPreferred: category funding amount in decimal currency units (for example, 100.00).
confirmation_tokenNoShort-lived, single-use token returned by the immediately preceding preview of this exact validated request.
budgeted_milliunitsNoRaw YNAB category funding amount in milliunits.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Adds significant behavioral context beyond annotations: two-step preview-execute pattern, error messages, and return values (updated category). No contradiction 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?

Front-loaded with purpose, well-organized with args, returns, examples, errors, and safety. Every sentence adds value without redundancy.

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 all aspects: purpose, all parameters, usage examples, error handling, and security. Output schema exists, so return values need not be fully detailed. Annotations provide additional context.

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?

Description explains each parameter meaning, relationships (e.g., budgeted_decimal vs milliunits), deprecation, and defaults, compensating for 43% of parameters lacking 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 'Update the budgeted amount for a category in the current month,' using a specific verb and resource, and distinguishes it from sibling update tools (e.g., for transactions).

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 clear context for use, including examples, error handling, and write safety (preview then execute). However, it does not explicitly compare to alternative tools like ynab_get_category or other update tools.

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