Twelvedata

Dividends

dividends

Read-onlyIdempotent

Twelve Data historical dividends for a stock / ETF symbol: ex-date, amount, frequency. Use for income analysis and dividend-capture strategies on Twelve-Data-covered symbols.

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	Default
`meta`	No
`dividends`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields 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."

removedOutput schema / properties / code

Removed value: -{
-  "description": "Response code",
-  "type": "number"
-}

addedOutput schema / properties / dividends

Added value: +{
+  "items": {
+    "properties": {
+      "amount": {
+        "type": "number"
+      },
+      "ex_date": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / message

Removed value: -{
-  "description": "Response message",
-  "type": "string"
-}

addedOutput schema / properties / meta

Added value: +{
+  "properties": {
+    "currency": {
+      "type": "string"
+    },
+    "exchange": {
+      "type": "string"
+    },
+    "exchange_timezone": {
+      "type": "string"
+    },
+    "mic_code": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "symbol": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "description": "Response status",
-  "type": "string"
-}

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"
+}

Changed2 schema fields changedMay 24, 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"
+}

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

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds context about the data source (Twelve Data) and that data is historical, but it does not disclose provider limitations, auth needs, or rate limits, which would add further value.

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?

Two sentences deliver the core data, provider, and intended use with no filler. The most important information is front-loaded.

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?

For a simple read-only historical data tool with a complete input schema, output schema, and safety annotations, the description is sufficient. Nothing critical is missing for an agent to invoke the tool correctly.

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 schema fully documents symbol, start_date, end_date, and exchange. The description's mention of stock/ETF symbol and historical data adds little beyond the schema, matching the baseline for fully documented parameters.

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 clearly identifies the tool as returning historical dividend data (ex-date, amount, frequency) for a stock or ETF symbol, which is a specific verb+resource. It does not explicitly contrast itself with sibling tools like earnings or splits, but the resource and fields make the purpose unambiguous.

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 states when to use the tool: for income analysis and dividend-capture strategies, and it notes the Twelve Data coverage constraint. It does not name alternative tools or state when not to use it, so it falls just short of a 5.

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.