Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Getaccountbyid

getAccountById

Retrieves a single YNAB account by plan ID and account ID so you can view its details.

Instructions

Returns a single account

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

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).
account_idYesThe id of the account

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/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 nothing about read-only semantics, permission/auth needs, error behavior for an invalid or deleted account id, or what fields come back. For a simple read this is lower risk than a mutation, but the disclosure gap is essentially total.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single four-word sentence with zero filler and the key noun front-loaded - efficient, though its brevity reflects under-specification rather than disciplined density.

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?

The tool is a low-complexity two-parameter lookup and the input schema is fully documented, so an agent can call it. With no output schema and no annotations, though, the description should at least hint at the returned account shape or failure modes, and it does neither.

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 coverage is 100%, including documentation of the "last-used" and "default" plan_id special values, so the schema already does the explanatory work. The description adds no meaning about required parameters or id semantics, which is the baseline-3 case when the schema 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 account" states a verb (returns/gets) and resource (account) and the word "single" hints at a by-id lookup versus the list-style getAccounts sibling. However it largely restates the tool name and never mentions the identifier it requires, so it sits at minimum-viable rather than genuinely distinguishing.

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, no exclusion, and no pointer to an alternative such as getAccounts for listing accounts or getTransactionsByAccount for related data. The agent must infer the retrieval context 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.