Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Updatecategory

updateCategory

Update an existing YNAB category's name, note, goal target, frequency, date, or group using its plan ID and category ID.

Instructions

Update a category

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plan_id": "<plan_id>",
      "category_id": "<category_id>",
      "category": "<category>"
    },
    "name": "updateCategory"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesThe id of the plan. "last-used" can be used to specify the last used plan and "default" can be used if default plan selection is enabled (see: https://api.ynab.com/#oauth-default-plan).
categoryYes
category_idYesThe id of the category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / category / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "category_group_id": {
      -        "description": "The id of the category group to which this category belongs.  An internal category group may not be specified.",
      -        "format": "uuid",
      -        "type": "string"
      -      },
      -      "goal_needs_whole_amount": {
      -        "description": "Whether the goal requires the full target amount each period. Only supported for 'NEED' goals. When true, the goal is configured as 'Set aside another...'. When false, the goal is configured as 'Refill up to...'.",
      -        "type": [
      -          "boolean",
      -          "null"
      -        ]
      -      },
      -      "goal_target": {
      -        "description": "The goal target amount in milliunits format.  If value is specified and goal has not already been configured for category, a monthly goal will be created for the category with this target amount.  If goal_type is not specified, it will default to 'NEED' or 'MF' for Credit Card Payment categories.",
      -        "format": "int64",
      -        "type": [
      -          "integer",
      -          "null"
      -        ]
      -      },
      -      "goal_target_date": {
      -        "description": "The goal target date in ISO format (e.g. 2016-12-01).",
      -        "format": "date",
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "name": {
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "note": {
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "category_group_id": {
      +        "description": "The id of the category group to which this category belongs.  An internal category group may not be specified.",
      +        "format": "uuid",
      +        "type": "string"
      +      },
      +      "goal_frequency": {
      +        "description": "When specified, configures a recurring 'NEED' target of goal_target that repeats at this frequency, replacing any existing target. Requires goal_target. 'yearly' also requires goal_target_date, the date the target is next due. 'monthly' accepts an optional goal_target_date, and 'weekly' cannot be combined with goal_target_date. Not supported for Credit Card Payment categories or categories paired to a loan account. Omit to leave an existing target's cadence unchanged.",
      +        "enum": [
      +          "monthly",
      +          "weekly",
      +          "yearly"
      +        ],
      +        "type": "string"
      +      },
      +      "goal_needs_whole_amount": {
      +        "description": "Whether the goal requires the full target amount each period. Only supported for 'NEED' goals, and not supported for Credit Card Payment categories or categories paired to a loan account. When true, the goal is configured as 'Set aside another...'. When false, the goal is configured as 'Refill up to...'.",
      +        "type": [
      +          "boolean",
      +          "null"
      +        ]
      +      },
      +      "goal_target": {
      +        "description": "The goal target amount in milliunits format.  If value is specified and goal has not already been configured for category, a monthly goal will be created for the category with this target amount.  If goal_type is not specified, it will default to 'NEED', or to 'MF' for Credit Card Payment categories and 'DEBT' for categories paired to a loan account. Must not be negative. When updating a category, passing null removes any existing target. Passing 0 does too, except for a Credit Card Payment category's 'TBD' (Pay Off Balance by Date) target, where 0 is a valid amount because the card's balance sets it. Use null to remove that target.",
      +        "format": "int64",
      +        "type": [
      +          "integer",
      +          "null"
      +        ]
      +      },
      +      "goal_target_date": {
      +        "description": "The goal target date in ISO format (e.g. 2016-12-01). Not supported for categories paired to a loan account. When combined with a goal_frequency of 'monthly' or 'yearly', this is the date the recurring target is next due. Required for yearly targets, so it cannot be removed from one.",
      +        "format": "date",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "name": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "note": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "object"
      +  }
      +]
  2. First observedv0.1.0

TDQS

D1.7/5.0
Behavior1/5

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

With no annotations present, the description carries the full behavioral burden and discloses nothing: it does not say this is a mutation, whether it is a partial or full update, what happens to omitted fields, or that setting goal fields can create or remove targets. An agent could easily invoke it expecting a simple rename and instead alter goal configuration.

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

Conciseness2/5

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

Three words are technically concise but amount to under-specification rather than efficiency; there is no structure, no front-loaded scope, and no sentence that conveys usable information beyond the title.

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

Completeness1/5

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

For a mutation tool with three required parameters, a nested goal-configuration object with non-obvious side effects, no annotations, and no output schema, a three-word description is completely inadequate. Nothing warns the agent that goal_target null/0 semantics or goal_frequency requirements can destroy or replace existing targets.

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

Parameters2/5

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

Schema description coverage is 67%, and the nested category object already documents name, note, goal_target, goal_frequency, and goal_target_date in detail. The description contributes no additional meaning about the plan_id sentinel values ("last-used", "default") or the interaction between goal fields.

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

Purpose2/5

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

"Update a category" restates the tool name updateCategory almost verbatim, giving only a verb and a resource with no scope details. It does not distinguish this tool from close siblings like updateCategoryGroup, updateMonthCategory, or createCategory.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (e.g., needing a plan_id), and no pointer to alternatives such as updateMonthCategory for month-specific budgeted amounts. The agent must infer everything from the sibling names.

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