Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Getmoneymovementgroupsbymonth

getMoneyMovementGroupsByMonth

Retrieves all money movement groups for a specified plan and month so you can review monthly budget flows.

Instructions

Returns all money movement groups for a specific month

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>",
      "month": "<month>"
    },
    "name": "getMoneyMovementGroupsByMonth"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYesThe plan month in ISO format (e.g. 2016-12-01) ("current" can also be used to specify the current calendar month (UTC))
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. 'Returns' implies a read, but nothing is said about permissions (e.g. plan access), pagination, ordering, whether empty months return an empty list, or what the response contains.

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?

A single front-loaded sentence with no filler. It is arguably too terse for a tool with no annotations, but nothing in it is wasted.

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

Completeness3/5

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

A simple two-parameter read with full schema coverage and no output schema, so the description needn't explain return values. However, with zero annotations and no mention of results or permissions, it leaves the agent with only a paraphrase of the name.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters (month, plan_id) are fully documented in the schema, including the 'current', 'last-used' and 'default' sentinels. The description adds only the notion of month scoping, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb ('Returns') and resource ('money movement groups') scoped to 'a specific month', which lets an agent distinguish it from the unfiltered getMoneyMovementGroups. It stops short of explicitly naming that sibling or clarifying the relationship.

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?

The phrase 'for a specific month' implies when the tool applies, but there is no explicit guidance on when to prefer it over getMoneyMovementGroups or getMoneyMovementsByMonth, and no prerequisites or exclusions are given.

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