Skip to main content
Glama
calebl

YNAB MCP Server

by calebl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Bulk Approve Transactions

ynab_bulk_approve_transactions
Idempotent

Approve multiple YNAB transactions in a single API call by providing an array of transaction IDs, reducing manual effort and speeding up budget reconciliation.

Instructions

Approves multiple transactions at once. Provide an array of transaction IDs to approve them all in a single API call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planIdNoThe plan ID (optional, defaults to YNAB_PLAN_ID; budgetId is a deprecated alias)
budgetIdNoDeprecated alias of planId (still accepted)
transactionIdsYesArray of transaction IDs to approve

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / budgetId / anyOf
      Added value: +[
+  {
+    "description": "Deprecated alias of planId (still accepted)",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / budgetId / description
      Previous value: -"The ID of the budget (optional, defaults to YNAB_BUDGET_ID environment variable)"New value: +"Deprecated alias of planId (still accepted)"
    • removedInput schema / properties / budgetId / type
      Removed value: -"string"
    • addedInput schema / properties / planId
      Added value: +{
+  "anyOf": [
+    {
+      "description": "The plan ID (optional, defaults to YNAB_PLAN_ID; budgetId is a deprecated alias)",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The plan ID (optional, defaults to YNAB_PLAN_ID; budgetId is a deprecated alias)"
+}
    • addedInput schema / properties / transactionIds / maxItems
      Added value: +500
    • addedInput schema / properties / transactionIds / minItems
      Added value: +1
  2. Addedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already carry the safety profile — readOnlyHint=false (mutating), idempotentHint=true, destructiveHint=false — so the bar is lower. The description adds the batch-execution trait ('all in a single API call') but discloses nothing about partial-failure semantics, behavior when some IDs are invalid or already approved, or the response shape. 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?

Two short sentences with zero filler. The first fronts the core purpose, the second names the required input and the efficiency benefit ('single API call'). Every sentence earns its place.

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

Completeness4/5

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

For a batch mutation, the combination is adequate: annotations cover mutation/idempotency/safety, the schema documents all parameters (including min/max items), and the description covers the batching behavior. The residual gaps — unspecified return value and atomicity on partial failure — are minor for this action and nothing needed to call it correctly is missing.

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%, so planId, budgetId, and transactionIds all already have descriptions in the schema; the baseline of 3 applies. The description's phrase 'array of transaction IDs' merely echoes the schema's own parameter description without adding format detail, limits, or the planId/budgetId relationship.

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 ('Approves') and resource ('multiple transactions'), and immediately scopes the action with 'at once' and 'in a single API call,' which implicitly separates it from the singular sibling ynab_approve_transaction. The purpose is unmistakable, though differentiation is implicit rather than explicit (no sibling is named).

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

Usage Guidelines3/5

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

The bulk framing ('multiple transactions at once,' 'single API call') tells an agent this is the batched path for approving transactions, so usage is implied. However, there is no explicit when-not-to-use guidance and no named alternative, such as pointing to ynab_approve_transaction for a single ID or noting the 500-item ceiling in prose.

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

Deploy Server

Other Tools