Skip to main content
Glama

ynab_export_transactions

Read-onlyIdempotent

Export YNAB budget transactions to a local JSON file, with optional filters for account and start date, to back up or analyze spending data.

Instructions

Export all transactions for a budget to a local JSON file.

Args:

  • budget_id (string, optional): Budget UUID. Omit to use the default budget.

  • account_id (string, optional): Filter by account.

  • since_date (string, optional): ISO date (YYYY-MM-DD) to filter transactions on or after.

Returns: file_path, transaction_count, file_size_kb

Examples:

  • Export all transactions: call with no args

  • Export account: set account_id

Errors:

  • "No default budget set" → run ynab_set_default_budget first

Input Schema

NameRequiredDescriptionDefault
typeNo
minimalNo
filenameNo
budget_idNo
account_idNo
since_dateNo
category_idNo

Output Schema

NameRequiredDescriptionDefault
messageYes
filenameYes
full_pathYes
export_modeYes
total_countYes
preview_countYes
minimal_fieldsYes
export_directoryYes
filename_explanationYes
preview_transactionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed26 schema fields changedv0.31.0
    • addedOutput schema / properties / preview_transactions / items / properties / account_id
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / account_name
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / amount / description
      Added value: +"Amount in decimal currency units"
    • addedOutput schema / properties / preview_transactions / items / properties / amount_currency
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / amount_formatted
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / amount_milliunits
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / approved
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / category_id
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / cleared
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / debt_transaction_type
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / deleted
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / flag_color
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / flag_name
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / import_id
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / import_payee_name
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / import_payee_name_original
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / matched_transaction_id
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / parent_transaction_id
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / payee_id
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / scheduled_transaction_id
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / subtransactions
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "amount": {
      +        "description": "Amount in decimal currency units",
      +        "type": "number"
      +      },
      +      "amount_currency": {
      +        "type": "number"
      +      },
      +      "amount_formatted": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "amount_milliunits": {
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      "category_id": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "category_name": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "deleted": {
      +        "type": "boolean"
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "memo": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "payee_id": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "payee_name": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "scheduled_transaction_id": {
      +        "type": "string"
      +      },
      +      "transaction_id": {
      +        "type": "string"
      +      },
      +      "transfer_account_id": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "transfer_transaction_id": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "amount"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / transaction_id
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / transfer_account_id
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / transfer_transaction_id
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview_transactions / items / properties / type
      Added value: +{
      +  "enum": [
      +    "transaction",
      +    "subtransaction"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / preview_transactions / items / required
      Previous value: -[
      -  "id",
      -  "date",
      -  "amount"
      -]New value: +[
      +  "id",
      +  "amount",
      +  "date"
      +]
  2. Changed8 schema fields changedv0.29.1
    • removedOutput schema / properties / minimal_fields / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / minimal_fields / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / preview_transactions / items / properties / category_name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / preview_transactions / items / properties / category_name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / preview_transactions / items / properties / memo / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / preview_transactions / items / properties / memo / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / preview_transactions / items / properties / payee_name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / preview_transactions / items / properties / payee_name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. Addedv0.26.9

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent, so the description earns credit for additive context: it discloses the local file-write side effect, the return keys (file_path, transaction_count, file_size_kb), and a specific error string with a remediation path. It omits where the file is written and whether an existing file is overwritten, which matters for an idempotent-flagged write-to-disk operation.

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?

Purpose is front-loaded in a single sentence, followed by clean Args/Returns/Examples/Errors sections with no filler. The Returns block is somewhat redundant given an output schema exists, but it is short and does not bloat the definition.

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?

For a 7-parameter tool with zero schema descriptions and no required fields, the description omits four parameters including a semantically significant enum and a default-true boolean. The file destination and overwrite behavior are also unstated, so an agent cannot fully predict the export's content or side effects from this definition.

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 0% across 7 parameters, so the description must compensate, and it documents only 3 (budget_id, account_id, since_date). The enum parameter 'type' (uncategorized/unapproved), the 'minimal' boolean defaulting to true, 'filename', and 'category_id' are entirely unexplained, leaving an agent unable to predict what those flags change about the export.

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

Purpose4/5

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

The first sentence states a specific verb+resource+output: exporting transactions from a budget to a local JSON file. That distinguishes it from mutation siblings, but it never names or contrasts with ynab_list_transactions, the closest read alternative, leaving the agent to infer the difference from 'local JSON file' alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The Examples block gives concrete invocation contexts ('call with no args' for everything, 'set account_id' to scope to an account), and the Errors block routes the agent to ynab_set_default_budget as a prerequisite. It stops short of explicit when-not guidance, e.g. when to use this versus ynab_list_transactions or ynab_analyze_spending.

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