List Yahoo Finance calendar
yahoo_finance_calendar_listRetrieve Yahoo Finance earnings, economic, split, and IPO calendar rows for a required date range. Filter by region or calendar type to plan event-driven research and market analysis.
Instructions
List Yahoo Finance earnings, economic, split and IPO calendar rows. Requires from and to. Returns a list (use cursor when paginated).
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": {
"from": "<from>",
"to": "<to>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "yahoo_finance_calendar_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Required. Window end: an ISO 8601 date or time. It is exclusive. Epoch seconds are also accepted. | |
| from | Yes | Required. Window start, as an ISO 8601 date or time (such as `2026-01-31`) or epoch seconds. A time with no zone is UTC. | |
| type | No | Calendar: `earnings`, `economic`, `splits` or `ipo`. Default: `earnings`. | |
| limit | No | Page size as an integer from 1 to 250. Default: 100. | |
| cursor | No | Cursor from `page.nextCursor` of the previous response. It only works with the same filters. | |
| offset | No | Zero-based position to begin the list at. Default: 0; maximum: 1,000,000. Only the first 10,000 rows are available; past that the page is empty. | |
| region | No | Market region, a two-letter code such as `US`, `GB` or `JP`. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| language | No | Language tag for names and news, e.g. `en-US` or `ja-JP`. | |
| llm_model | Yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess. | |
| conversation_id | No | Echo the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it. |