Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Createpayee

createPayee

Add a new payee to a YNAB plan by supplying the plan ID and payee name, enabling you to track transactions for that vendor or recipient.

Instructions

Creates a new 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": "<payee>"
    },
    "name": "createPayee"
  }
}

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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/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 burden, and it only conveys that a write occurs. It does not disclose auth/permission requirements, whether duplicate payee names are allowed, what happens on invalid plan_id, or whether the created payee is returned — all things the schema cannot express.

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 front-loaded and contains no filler, but it is under-specified rather than genuinely concise — there is essentially no content to structure.

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?

For a two-parameter mutation with a nested object, no output schema and no annotations, the definition leaves important gaps: no return-value expectation, no error/validation behavior, and no guidance on the nested payee payload. It is minimal but not actively wrong.

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 description coverage is only 50%: plan_id is documented inline (including the 'last-used'/'default' sentinels), but the nested payee object has no description of its own. The description adds no meaning beyond the schema and does not compensate for the undocumented nested object.

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 is a near-restatement of the tool name: 'createPayee' -> 'Creates a new payee'. It names the verb and resource but adds no scope, no distinguishing detail versus siblings like updatePayee or createAccount, and an agent gains 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 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 mention of prerequisites (e.g. a valid plan_id), and no pointer to alternatives such as updatePayee for existing payees. The agent must infer selection purely from the tool name.

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