Skip to main content
Glama

bulk_update_transactions

Update multiple transactions at once. Provide transactionIds plus at least one of categoryId, tagIds, note, payeeId (null clears the payee), or excludeFromStats. Tags can be added to, removed from, or replaced on all specified transactions. Requires finance:write scope.

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": {
      "transactionIds": "<transactionIds>"
    },
    "name": "bulk_update_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoNote to set on all transactions
tagIdsNoTag IDs to apply according to tagMode
payeeIdNoID of an existing payee to link to all transactions (from get_payees). Pass null to clear the payee
tagModeNoHow to apply tagIds: add (default) appends, replace overwrites, remove removes those tags
categoryIdNoNew category ID to assign to all transactions
transactionIdsYesIDs of transactions to update
excludeFromStatsNotrue keeps the transactions out of reports and stats without removing them; false brings them back

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / excludeFromStats
      Added value: +{
      +  "description": "true keeps the transactions out of reports and stats without removing them; false brings them back",
      +  "type": "boolean"
      +}
  2. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / categoryId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • changedInput schema / properties / payeeId / anyOf
      Previous value: -[
      -  {
      -    "format": "uuid",
      -    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "format": "uuid",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / payeeId / description
      Previous value: -"Payee ID to assign to all transactions. Pass null to clear"New value: +"ID of an existing payee to link to all transactions (from get_payees). Pass null to clear the payee"
    • removedInput schema / properties / tagIds / items / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / transactionIds / items / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Changed1 schema field changed
    • addedInput schema / properties / note / maxLength
      Added value: +1000
  4. Changed1 schema field changed
    • addedInput schema / properties / payeeId
      Added value: +{
      +  "anyOf": [
      +    {
      +      "format": "uuid",
      +      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Payee ID to assign to all transactions. Pass null to clear"
      +}
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=false, so the description carries real weight and delivers: the write scope needed, the null-clears-payee convention, and the tagMode add/replace/remove distinctions. It does not disclose whether the bulk write is atomic when some transactionIds are invalid, or whether the change is reversible — the main behavioral gap for a mutating bulk tool.

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

Conciseness5/5

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

Three sentences, front-loaded with the action and scope, then the required argument shape, then the auth requirement. No restatement of the tool name and no filler.

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

Completeness4/5

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

For a 7-parameter bulk mutation with no output schema and only a readOnlyHint annotation, the description covers prerequisites, auth scope, and the trickiest parameter interactions. The remaining gap is failure behavior across multiple IDs (partial success vs all-or-nothing), which an agent would want before calling this on a large batch.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by imposing the 'at least one of' constraint across parameters, which no individual schema field expresses. It also reiterates the payee-null semantics and tag mode behavior in context. It adds no format or limit detail beyond the schema.

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 description opens with a specific verb and resource, 'Update multiple transactions at once', which makes the bulk scope explicit and separable from single-record update siblings. It then enumerates the updatable fields. It does not explicitly name the single-transaction alternative, so sibling differentiation relies on the word 'multiple'.

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?

'Provide transactionIds plus at least one of categoryId, tagIds, note, payeeId, or excludeFromStats' states the precondition for a valid call and rules out an empty update. 'Requires finance:write scope' adds a gating requirement. No explicit when-not guidance or rate-limit context is given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.