Twelvedata

Earnings

earnings

Read-onlyIdempotent

Twelve Data earnings history and upcoming earnings dates for a stock symbol: EPS estimate, EPS actual, surprise percentage, and report date per quarter.

Input Schema

TableJSON Schema

Name	Required	Description
`symbol`	Yes	Ticker/symbol. Stocks e.g. "AAPL", "MSFT"; forex "EUR/USD"; crypto "BTC/USD"; ETFs "SPY". Comma-separate for a batch (e.g. "AAPL,MSFT"). Market indices (SPX, N225, …) need a Grow-or-higher Twelve Data key passed via _apiKey — the shared key cannot quote them.
`end_date`	No	Optional end of range, "YYYY-MM-DD" or "YYYY-MM-DD HH:MM:SS".
`exchange`	No	Optional exchange filter (e.g. "NASDAQ", "NYSE", "Binance").
`start_date`	No	Optional start of range, "YYYY-MM-DD" or "YYYY-MM-DD HH:MM:SS".

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	Response code
`status`	No	Response status
`message`	No	Response message

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedInput schema / properties / symbol / description

Previous value: -"Ticker/symbol. Stocks e.g. \"AAPL\", \"MSFT\"; forex \"EUR/USD\"; crypto \"BTC/USD\"; ETFs \"SPY\"; indices \"IXIC\". Comma-separate for a batch (e.g. \"AAPL,MSFT\")."New value: +"Ticker/symbol. Stocks e.g. \"AAPL\", \"MSFT\"; forex \"EUR/USD\"; crypto \"BTC/USD\"; ETFs \"SPY\". Comma-separate for a batch (e.g. \"AAPL,MSFT\"). Market indices (SPX, N225, …) need a Grow-or-higher Twelve Data key passed via _apiKey — the shared key cannot quote them."

Changed4 schema fields changedJun 24, 2026

addedInput schema / properties / end_date

Added value: +{
+  "description": "Optional end of range, \"YYYY-MM-DD\" or \"YYYY-MM-DD HH:MM:SS\".",
+  "type": "string"
+}

addedInput schema / properties / exchange

Added value: +{
+  "description": "Optional exchange filter (e.g. \"NASDAQ\", \"NYSE\", \"Binance\").",
+  "type": "string"
+}

addedInput schema / properties / start_date

Added value: +{
+  "description": "Optional start of range, \"YYYY-MM-DD\" or \"YYYY-MM-DD HH:MM:SS\".",
+  "type": "string"
+}

addedInput schema / properties / symbol

Added value: +{
+  "description": "Ticker/symbol. Stocks e.g. \"AAPL\", \"MSFT\"; forex \"EUR/USD\"; crypto \"BTC/USD\"; ETFs \"SPY\"; indices \"IXIC\". Comma-separate for a batch (e.g. \"AAPL,MSFT\").",
+  "type": "string"
+}

Changed1 schema field changedMay 24, 2026
- removedInput schema / additionalProperties
```
Removed value: -true
```

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "symbol": "AAPL"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "code": {
+      "description": "Response code",
+      "type": "number"
+    },
+    "message": {
+      "description": "Response message",
+      "type": "string"
+    },
+    "status": {
+      "description": "Response status",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already communicate read-only, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds useful context such as the data source and the returned metrics, but it omits caveats like batch-symbol support and any credential limitations, which are left to the schema.

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 a single, information-dense sentence with no filler. It front-loads the resource, source, and key output fields, making it easy to scan and understand quickly.

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 read-only tool with one required parameter, a rich symbol schema, and an output schema, the description is mostly sufficient: it names the data scope and the returned fields. It loses the top score only because it omits guidance about batch symbols and does not point to earnings_calendar for broader earnings-date queries.

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 the input schema fully documents symbol, start_date, end_date, and exchange. The description itself adds no parameter-level detail, so the baseline score of 3 is appropriate.

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?

The description identifies the resource clearly: Twelve Data earnings history and upcoming earnings dates for a stock symbol, with specific fields (EPS estimate, EPS actual, surprise percentage, report date). It stops short of a 5 because it lacks an explicit verb like 'retrieves' or 'lists' and does not differentiate itself from the sibling earnings_calendar.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for a stock symbol' implies a single-symbol earnings lookup, which gives some usage context. However, there is no explicit statement about when to use this tool versus alternatives like earnings_calendar, dividends, or splits, and no when-not-to-use guidance.

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

All Twelvedata tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.