Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Getmoneymovementsbymonth

getMoneyMovementsByMonth

Retrieve all money movements for a specified YNAB plan and month using the plan ID and ISO month, enabling clear monthly cash-flow review.

Instructions

Returns all money movements 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": "getMoneyMovementsByMonth"
  }
}

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

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It conveys only that the result is a complete set of movements for one month; it says nothing about permissions/scopes needed, whether results are paginated or bounded, whether empty months error or return empty, or what happens with the "current"/"last-used" shortcuts.

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?

One front-loaded sentence with the resource and its scope; nothing redundant or padded.

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?

For a simple two-parameter read with a fully documented schema and no output schema, the definition is minimally viable. It leaves out behavioral context that annotations would normally supply (errors, limits, empty results), which matters because no annotations exist here.

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 are documented there, including the ISO format and the "current"/"last-used"/"default" sentinels. The description adds no meaning beyond that, 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?

The description states a specific verb ("Returns") and resource ("all money movements") plus a scope ("for a specific month"), so the agent knows exactly what data comes back. It does not distinguish itself from close siblings like getMoneyMovements or getMoneyMovementGroupsByMonth, so it stops short of a 5.

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?

"for a specific month" implies the required scope but gives no when-to-use guidance, no prerequisites, and no named alternative. An agent browsing the sibling list has to infer from names alone whether this or getMoneyMovementGroupsByMonth is appropriate.

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