Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Deletetransaction

deleteTransaction

Deletes a YNAB transaction using its transaction ID and plan ID, letting you remove unwanted or duplicate entries from a budget.

Instructions

Deletes a transaction

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

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).
transaction_idYesThe id of the transaction

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/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 behavioral burden, yet it discloses none of the critical traits: whether deletion is permanent or reversible, whether it requires plan write permissions, whether the transaction must not be reconciled, or how balances are affected. The single word "Deletes" is all that is added.

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 description is a single well-formed sentence with zero padding, which is front-loaded, but its brevity stems from under-specification rather than efficient communication of necessary detail.

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

Completeness2/5

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

This is a destructive mutation with no annotations and no output schema to lean on, so the description should at minimum state irreversibility, required permissions, and failure conditions. It covers none of these, leaving an agent unable to judge the consequences of invoking it.

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 the schema itself explains plan_id (including the "last-used" and "default" sentinels) and transaction_id thoroughly. The description adds no meaning beyond that, so the baseline of 3 applies.

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?

"Deletes a transaction" restates the tool name (deleteTransaction) and title (Deletetransaction) verbatim, offering no scope, identifier context, or differentiation from deleteScheduledTransaction. An agent learns nothing it could not infer from the name alone.

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

Usage Guidelines1/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 exclusions, and no mention of the closely named sibling deleteScheduledTransaction, which a careless agent could easily confuse with this one. No prerequisites or conditions are stated.

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