Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Deletescheduledtransaction

deleteScheduledTransaction

Deletes a scheduled transaction from a YNAB plan using plan and scheduled transaction IDs, removing it from upcoming scheduled activity.

Instructions

Deletes a scheduled 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>",
      "scheduled_transaction_id": "<scheduled_transaction_id>"
    },
    "name": "deleteScheduledTransaction"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/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, and it discloses nothing. It does not state that the deletion is permanent and irreversible, whether existing matched transactions are affected, or what permissions are required. For a destructive mutation tool this is a serious gap.

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 single sentence is efficiently front-loaded with the action, but its brevity comes from under-specification rather than disciplined editing. There is no wasted wording, but nothing of substance is said either.

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?

The tool is structurally simple (two required string params, fully documented schema, no output schema), but it is a destructive mutation with zero annotation coverage. The description should at minimum state that the deletion cannot be undone; it does not.

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 already explains plan_id (including the 'last-used' and 'default' sentinels) and scheduled_transaction_id. The description adds no meaning beyond the schema, 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?

The description 'Deletes a scheduled transaction' is a tautological expansion of the tool name and title, restating the verb and resource without adding any distinguishing detail. It does not differentiate this from the sibling deleteTransaction or explain the scheduled-transaction scope.

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?

No when-to-use guidance is provided. The description never clarifies the difference between deleting a scheduled transaction and deleting an actual transaction, nor does it mention prerequisites such as confirming the scheduled transaction exists. Usage must be inferred entirely from the name.

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