Skip to main content
Glama

search_transactions

Read-only

Search and filter transactions. Returns transaction amount (original + base currency), category, account, payee (payeeId and payee { id, name }), note, date, type, and tags. Filter by payee with payeeIds (get_payees resolves a name to an id) and by planned state with isPlanned. Use date filters to limit results. Default: last 30 days, 50 items; future plans need a later endDate.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default: 50, max: 500)
orderNoSort order by date (default: desc)
offsetNoPagination offset (default: 0)
searchNoSearch in transaction notes
tagIdsNoFilter by tag IDs
endDateNoEnd date (ISO 8601). Default: now, which hides planned (future-dated) transactions. Set it to a future date to see upcoming plans
payeeIdsNoFilter by payee (merchant) IDs. Use get_payees to resolve a merchant name to its id
amountMaxNoMaximum amount (decimal, in original currency)
amountMinNoMinimum amount (decimal, in original currency)
isPlannedNotrue: only your planned transactions (upcoming, not yet confirmed); false: only real ones. Omit for real ones plus your plans. Plans are dated in the future, so also set endDate beyond them
startDateNoStart date (ISO 8601). Default: 30 days ago
accountIdsNoFilter by account IDs
categoryIdsNoFilter by category IDs
excludeRefundsNoExclude refund transactions
transactionTypeNoFilter by transaction type
excludeTransfersNoExclude transfer transactions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / accountIds / 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 / categoryIds / 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)$"
    • changedInput schema / properties / endDate / description
      Previous value: -"End date (ISO 8601). Default: today"New value: +"End date (ISO 8601). Default: now, which hides planned (future-dated) transactions. Set it to a future date to see upcoming plans"
    • addedInput schema / properties / isPlanned
      Added value: +{
      +  "description": "true: only your planned transactions (upcoming, not yet confirmed); false: only real ones. Omit for real ones plus your plans. Plans are dated in the future, so also set endDate beyond them",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / payeeIds
      Added value: +{
      +  "description": "Filter by payee (merchant) IDs. Use get_payees to resolve a merchant name to its id",
      +  "items": {
      +    "format": "uuid",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • 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)$"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the safety profile is already covered. The description adds genuinely useful behavioral detail beyond that: the implicit 30-day/50-item defaults and the non-obvious trap that the default endDate of "now" silently hides future-dated planned transactions unless endDate is extended.

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?

The description is three dense sentences: capability plus return shape first, then the two non-obvious filter mechanics, then the default-behavior caveat. Every sentence carries information, though the return-field enumeration is long and partially duplicates what the schema's parameter names imply.

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 16-parameter query tool with no output schema, the description does the heavy lifting by naming the returned fields and flagging the two gotchas (payee id resolution, planned transactions hidden by the default endDate). Pagination and sorting are left to the schema, which documents them adequately, so nothing critical is missing.

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 description coverage is 100%, so every one of the 16 parameters is already documented, including the isPlanned and endDate interaction. The description restates the payeeIds/get_payees and isPlanned semantics already present in the schema rather than adding syntax or format guidance, so the baseline 3 applies.

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?

"Search and filter transactions" gives a specific verb plus resource, and the description enumerates what comes back (amount in original + base currency, category, account, payee, note, date, type, tags), so an agent knows this is the read/query tool for transaction lists. It does not explicitly contrast itself with close siblings such as get_transactions_by_id or get_transactions_summary, so it stops short of full sibling differentiation.

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?

It states concrete operating context: default window of last 30 days and 50 items, and that future plans require pushing endDate beyond now. It also routes the agent to get_payees to resolve a merchant name before filtering by payeeIds. There is no explicit "use this instead of X" exclusion, which keeps it below a 5.

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.