ynab-mcp

import_transactions

Import available transactions from all linked accounts in a YNAB plan and return their transaction IDs. Use the plan ID to sync new bank activity before budgeting.

Instructions

Import available transactions on all linked accounts for the given plan.

Equivalent to clicking 'Import' on each account in the YNAB web app or tapping the 'New Transactions' banner in the mobile app. Returns the list of transaction IDs that were imported.

Args: plan_id: The plan ID (use list_plans to find available IDs)

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

Input Schema

Name	Required	Description	Default
`plan_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries full responsibility. It discloses that the tool returns a list of imported transaction IDs and implies a batch operation on all linked accounts. However, it does not mention potential side effects such as the possibility of duplicate imports, rate limits, or the need for account linkage, leaving gaps in transparency.

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?

The description is concise, with a clear opening sentence followed by a helpful analogy and a structured Args section. Every sentence is purposeful, and there is no extraneous information, making it easy to scan.

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

Completeness5/5

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

Given the low complexity (1 required parameter, output schema exists), the description covers the tool's purpose, parameter guidance, and return value sufficiently. The output schema handles return structure details, so no further elaboration is needed.

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

Parameters4/5

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

There is only one parameter (plan_id) with 0% schema description coverage. The description compensates by explaining what plan_id is and directing the user to 'list_plans' to find available IDs, adding meaningful context that the schema alone lacks.

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

Purpose5/5

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

The description clearly states the tool imports transactions on all linked accounts, using a specific verb ('Import') and resource ('transactions on linked accounts'). The analogy to clicking 'Import' in the web app or mobile app reinforces the purpose and distinguishes it from sibling tools like 'create_transaction' or 'list_transactions'.

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

Usage Guidelines4/5

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

The description provides a usage analogy ('Equivalent to clicking Import...') and instructs on how to find the plan_id using 'list_plans'. However, it does not explicitly state when not to use this tool vs. alternatives like manual transaction creation, nor does it mention any prerequisites or limitations.

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

Deploy Server