Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Updatepayee

updatePayee

Modify an existing payee's name in a YNAB plan by providing the plan ID, payee ID, and new name.

Instructions

Update a payee

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>",
      "payee_id": "<payee_id>",
      "payee": "<payee>"
    },
    "name": "updatePayee"
  }
}

Input Schema

NameRequiredDescriptionDefault
payeeYes
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).
payee_idYesThe id of the payee

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.7/5.0
Behavior1/5

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

No annotations exist, so the description carries the full behavioral burden, yet it discloses nothing: not whether this is PUT-style replacement or partial merge, whether omitted fields are cleared, whether the payee must belong to the given plan, or what permissions/errors apply. A three-word phrase leaves every mutation-specific behavior an agent needs entirely undocumented.

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

Conciseness2/5

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

The single phrase is not verbose, but it is under-specified rather than concise: it front-loads nothing and there is no structure to guide an agent. Length is only appropriate because there is essentially no content.

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

Completeness1/5

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

This is a mutation tool with a nested required object, three required parameters, no annotations, and no output schema, so the description was the only place to convey replace-vs-patch semantics and validation behavior. It conveys none of that, making the definition inadequate for the tool's complexity.

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

Parameters2/5

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

Schema coverage is 67% and the payee parameter is a nested object whose only documented child is name; the description adds no meaning about the nested structure or how payee_id/plan_id interact with it. Since the schema already documents plan_id and payee_id, the description contributes no additional parameter semantics on top of it.

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?

"Update a payee" is effectively a restatement of the tool name and title, adding no scope beyond the verb+resource. It does not say what fields can be updated, whether the update is partial or a full replacement, or how it differs from createPayee or getPayeeById.

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 prerequisites, and no mention of alternatives such as createPayee (for new payees) or getPayeeById (for reads). The agent must infer usage purely from the name.

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