List backtests
list_backtestsSummarize recent backtests for the user, optionally scoped to a strategy or conversation. For the current attached strategy, use scope='strategy' and omit id, strategyId, and aiStrategyId. The server resolves the exact strategy from the scoped MCP token, avoiding copied-identifier errors. Supports server-side sorting via sortBy + sortOrder (default is createdAt desc). Use status to filter by one or more backtest statuses (comma-separated). Use offset+limit to page through full history (for example, limit=50 offset=0, then offset=50 for older runs). For lightweight summaries, includeArtifacts defaults to false; set includeArtifacts=true only when you need artifact manifests inline (artifact pages are capped to 10 rows). If a backtest status is initiated/in_progress/backtesting, only status/log diagnostics may be available; do not fetch trades.csv, indicators.csv, or stats.csv until the run reaches a terminal status. The response includes a 'Tool IDs' section listing full backtestId/revisionId/aiStrategyId/strategyId for each row so downstream tools can chain without manual lookup. For normal questions about 'this backtest', 'the backtest', or 'how did it do', select one relevant terminal run from this response and keep that same backtestId for every get_backtest_artifact, get_backtest_logs, and query_csv call in the answer. Only inspect multiple run ids when the user asks for all runs, a comparison, or a different named run. If the user or conversation history already gives an exact backtest id, list_backtests is optional discovery only and does not replace direct artifact/log inspection. If this response is empty, still use the explicit id with get_backtest_artifact/get_backtest_logs/backtest_status/query_csv when diagnosing that named run. Do not replace a user-provided backtest id with a newer or listed run unless the user asks for latest, comparison, or a different named run. IMPORTANT: Each backtest has TWO date concepts: (1) 'createdAt' = when the backtest was RUN (e.g., '2024-12-08T22:48:17Z'), (2) 'period'/'startDate'/'endDate' = the historical date RANGE the backtest covers (e.g., '2024-01-01 → 2024-12-01'). When user asks for 'most recent' or 'latest' backtest, use createdAt to determine recency, NOT the period. COMMUNICATION: When referring to backtests, NEVER use the backtest ID (meaningless to users). Instead describe it by WHEN it ran and WHAT it covers, e.g.: 'The backtest that ran at 5:48 PM covering Dec 2024 to Dec 2025...' Convert createdAt timestamps to the user's timezone for communication.
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": "list_backtests"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | With scope "all" (default): one exact backtest id; returns that run if you own or ran it, otherwise nothing. With scope "conversation": the conversation id. With scope "strategy": a strategy or aiStrategy id. | |
| limit | No | ||
| scope | No | all | |
| offset | No | ||
| sortBy | No | Server-side sort field. Supported values: createdAt, totalReturn, cagrAnnualReturn, sharpe, maxDrawdown, status. | createdAt |
| status | No | Optional comma-separated status filter. Valid values: initiated, in_progress, completed, completed_no_trades, failed, force_stopped, terminated_timeout, not_found, completed_with_errors. Do not use deployment-only statuses such as terminated. Example: completed,completed_no_trades. | |
| sortOrder | No | Sort direction: desc (default) or asc. | desc |
| strategyId | No | ||
| aiStrategyId | No | ||
| includeArtifacts | No | Include artifact manifests in each backtest item (default false to keep responses lightweight). |