Monarch Money MCP Server

Overview Schema Source Related Servers Discussions Admin

Search Transactions

search_transactions

Read-only

Search transactions by keyword and filter by date, account, category, tags, and other criteria. Returns matching transactions plus search metadata for pagination.

Instructions

Search one page of transactions using Monarch's text search.

Args: query: Nonempty search text for Monarch's transaction search. limit: Maximum transactions to request (default: 500). offset: Transactions to skip for pagination. start_date: Inclusive start, accepting ISO dates or natural language. Without end_date, the end defaults to today. end_date: Inclusive end. Without start_date, the start defaults to the first day of the end date's month. account_id: Account ID from get_accounts. category_id: Category ID from get_transaction_categories. tag_ids: Comma-separated tag IDs. has_attachments: Filter by attachment presence. has_notes: Filter by notes presence. hidden_from_reports: True for hidden transactions, False for visible ones. is_split: Filter by split status. is_recurring: Filter by recurring status. is_pending: True for pending transactions, False for posted transactions. verbose: False uses get_transactions' compact fields; True keeps full API objects.

Boolean filters default to None (no restriction). Returns matching transactions and search_metadata with the query, this page's result_count, and applied filters. Use offset for further pages; result_count is not the total number of matches.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`offset`	No
`tag_ids`	No
`verbose`	No
`end_date`	No
`is_split`	No
`has_notes`	No
`account_id`	No
`is_pending`	No
`start_date`	No
`category_id`	No
`is_recurring`	No
`has_attachments`	No
`hidden_from_reports`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`transactions`	Yes
`search_metadata`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.5.0Sep 24, 2026

addedInput schema / properties / is_pending

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Is Pending"
+}

First observedv0.3.2May 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already mark this as read-only, and the description adds significant behavioral detail: returning search_metadata, applied filters, the compact-field option via verbose, and the crucial caveat that result_count is page-specific, not total matches. This goes well beyond the structured annotations.

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?

The description is front-loaded with a one-sentence summary, then uses a tight Args list to document a large parameter set without fluff. Every line adds operational value, and the pagination caveat is placed exactly where relevant.

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

Completeness5/5

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

Despite high complexity (15 parameters, no schema descriptions), the description covers all parameter semantics, defaults, pagination, and the shape of the response metadata. An agent has everything needed to invoke the tool correctly.

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

Parameters5/5

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

With 0% schema description coverage, the description carries full responsibility for all 15 parameters. The Args block explains each one, including defaults, date-range fallbacks, source tools for ID parameters, and the meaning of boolean filters. This fully compensates for the schema gap.

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

Purpose5/5

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

The opening sentence states a specific verb ('Search'), a resource ('transactions'), and a scope ('one page... using Monarch's text search'). This clearly identifies the tool's function and differentiates it from sibling tools like get_transactions without needing to inspect schemas.

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 description clearly establishes the text-search use case and pagination behavior ('Use offset for further pages; result_count is not the total number of matches'). It does not explicitly mention alternatives or when not to use it, but the context is clear enough for an agent to select it appropriately.

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