Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Updatecategorygroup

updateCategoryGroup

Update a YNAB category group’s name by specifying the plan, group ID, and new name. Use it to correct or rename budget category groups in a plan.

Instructions

Update a category group

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_group_id": "<category_group_id>",
      "category_group": "<category_group>"
    },
    "name": "updateCategoryGroup"
  }
}

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).
category_groupYes
category_group_idYesThe id of the category group

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses nothing: not whether this replaces or merges the group, not what happens to existing categories in the group, not permission or plan-context requirements, and not what is returned. For a mutation tool this is a critical gap.

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

Conciseness3/5

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

The single sentence contains no filler, but that is because it contains almost no information. It is concise at the cost of being under-specified rather than front-loading useful detail.

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?

The tool is a mutation with a nested required object, no annotations, and no output schema, so the description is the only source of behavioral context. It provides none of what an agent needs to call this safely and correctly.

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 coverage is 67%, and the description adds no meaning for any of the three required parameters. It does not explain the "last-used"/"default" sentinel values for plan_id, nor the nested category_group object whose name is capped at 50 characters.

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 group" is a verb+resource phrase, but it merely restates the tool name and title in prose. It adds no scope detail (which fields, whole-object vs partial) and gives no cue distinguishing it from siblings like createCategoryGroup or updateCategory.

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 such as plan selection, and no reference to alternatives. An agent must infer everything about invocation context from the name alone.

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