TradingView MCP

by moeuu

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Capture a TradingView chart for an exact date range

tradingview_capture_period

Read-onlyIdempotent

Capture a TradingView chart for a specified symbol and date range, returning the chart as a PNG image.

Instructions

Open an official TradingView symbol and interval, use the Supercharts Custom range control for the requested YYYY-MM-DD dates, and return the resulting chart as a PNG in one call. The browser closes by default and authentication remains local.

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": {
      "symbol": "<symbol>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "tradingview_capture_period"
  }
}

Input Schema

Name	Required	Description	Default
`to`	Yes	Last visible calendar date, in YYYY-MM-DD format.
`from`	Yes	First visible calendar date, in YYYY-MM-DD format.
`width`	No
`height`	No
`symbol`	Yes	TradingView symbol, preferably EXCHANGE:TICKER such as NASDAQ:AAPL.
`interval`	No		D
`layoutId`	No
`chartOnly`	No
`keepBrowserOpen`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive traits, so the description only needs to add extra context. It usefully discloses that the browser closes by default and that authentication remains local, which are meaningful behavioral details beyond the annotations.

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 tightly written sentences that front-load the core action and output type, then add one essential behavioral note. Every clause earns its place with no filler.

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 tool with nine parameters and no output schema, the description is reasonably complete: it states the main inputs, the output format (PNG), the single-call behavior, and browser/auth behavior. It does not detail every optional parameter, but the schema supplies defaults and types for most.

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 descriptions cover only 33% of parameters, so the description needs to compensate. It clarifies the role of symbol, interval, from/to dates, and indirectly keepBrowserOpen via 'browser closes by default,' but leaves width, height, chartOnly, and layoutId unexplained.

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 names a specific verb-plus-resource action: open TradingView symbol/interval, apply a custom date range, and return the chart as PNG in one call. It clearly distinguishes this from sibling snapshot/export tools by emphasizing exact YYYY-MM-DD range capture.

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 gives clear context for when to use the tool: when a chart PNG for an exact date range is needed in a single call. It does not name alternatives or explicit exclusions, but the exact-range and one-call focus is sufficient practical guidance.

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