Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Gettransactionbyid

getTransactionById

Retrieve a single YNAB transaction by plan ID and transaction ID to inspect its details and verify specific budget activity.

Instructions

Returns a single 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": "getTransactionById"
  }
}

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

C2.6/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and delivers almost nothing beyond the word "Returns," which weakly implies a read. It does not disclose auth requirements, error behavior for an unknown transaction_id, or whether the lookup is scoped to a plan.

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?

One short sentence, front-loaded and free of filler, so nothing is wasteful. But the brevity comes at the cost of under-specification rather than economy of expression.

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?

This is a simple two-required-parameter read with fully documented schema fields and no output schema, so an agent can construct the call. Still, nothing is said about the returned transaction shape or failure modes, which leaves the definition only minimally adequate.

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%, including the meaningful "last-used"/"default" sentinel values for plan_id, so the schema already does the semantic work. The description adds no parameter meaning of its own, which is the expected baseline when coverage is complete.

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

Purpose3/5

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

"Returns a single transaction" states a clear verb and resource, and the word "single" hints at the singular-fetch distinction from list siblings such as getTransactions. However, it never names or contrasts with those siblings, so the differentiation is only implied rather than stated.

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?

There is no when-to-use guidance at all: nothing about when to pick this over getTransactions, getTransactionsByAccount, or the other filtered list tools. The only contextual hint is the required plan_id/transaction_id pair, which comes from the schema, not the description.

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