TradingView MCP

Overview Schema Source Related Servers Discussions Admin

Export TradingView chart data

tradingview_export_chart

Export chart data from TradingView Supercharts, including visible indicator columns, and optionally load OHLCV into a local chart for deterministic analysis.

Instructions

Download the data currently loaded in official Supercharts through its chart-data export UI, including visible indicator columns. Optionally load OHLCV into the local chart for deterministic analysis.

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": "tradingview_export_chart"
  }
}

Input Schema

Name	Required	Description	Default
`loadChart`	No
`outputName`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 20, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations indicate readOnlyHint=false and openWorldHint=true, and the description adds transparency by explaining side effects: it uses the chart-data export UI and optionally loads OHLCV into the local chart. This goes beyond the annotations, though it does not mention file output location or return behavior.

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 two sentences, front-loaded with the main action and optional behavior. Every word earns its place with no padding or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core purpose and one side effect, but lacks prerequisites (e.g., chart must be open), what the output format is, and what 'loadChart' does to existing data. Without an output schema, this leaves important gaps for an autonomous agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain parameters. It implicitly explains loadChart via 'Optionally load OHLCV into the local chart', but outputName is not mentioned at all. For a 2-param tool, this incomplete compensation is insufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool downloads chart data currently loaded in official Supercharts via its chart-data export UI, including visible indicator columns. This specific verb+resource+scope distinguishes it from sibling tools like tradingview_get_history or tradingview_snapshot.

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 implies when to use the tool: when you need the currently loaded chart data with indicators, and optionally to load OHLCV for deterministic analysis. It provides context but does not explicitly mention alternative tools or exclusion cases, earning a 4.

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