List journal trades
journal_list_tradesTrade summaries — key, account, symbol, asset class, direction, status (open/win/loss/breakeven), open and close times, quantity and open quantity, average entry/exit, gross and net P&L, fees, fill count, duration, realized R, tags, rating, reviewed flag, hasNotes — newest-opened first by default. sort orders by any of openedAt, closedAt, netPnl, grossPnl, durationMs, quantity, symbol or rating (names match the response fields); order is desc unless set, except symbol which defaults to asc. Trades lacking the sort value (open trades for closedAt/durationMs, unrated for rating) come last in either order; netPnl is after fees, grossPnl before. Filter by account ids, open-day window (from/to are inclusive YYYY-MM-DD day keys in the journal timezone, applied to the trade's open day; open positions are always listed), symbol, direction, status or one exact tag. Keyset-paginated: pass nextCursor back as cursor with the same sort, order and filters. Examples: biggest winners this month = from/to + sort netPnl; worst by gross = sort grossPnl, order asc, status loss; longest holds = sort durationMs. Summaries carry no fills or note text: journal_get_trade with the key has those. Requires signing in with a LuxAlgo account (OAuth).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Inclusive end day (YYYY-MM-DD, journal timezone). Overrides `range`. | |
| tag | No | Trades carrying exactly this tag (see journal_list_tags). | |
| from | No | Inclusive start day (YYYY-MM-DD, journal timezone). Overrides `range`. | |
| sort | No | Field to order by; default openedAt. Trades without a value for it come last in either order. | |
| limit | No | Page size, default 25. | |
| order | No | Default desc (largest / latest first); symbol defaults to asc (A→Z). | |
| cursor | No | `nextCursor` from the previous page; keep every other argument identical. | |
| status | No | ||
| symbol | No | One symbol, e.g. 'AAPL' (case-insensitive). | |
| context | Yes | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." | |
| accounts | No | Journal account ids to scope to (from journal_list_accounts). Omit for every account, archived ones included. Unknown ids are rejected. | |
| direction | No |