TradingView MCP

Overview Schema Source Related Servers Discussions Admin

Remove custom chart series

chart_remove_series

Remove a custom line or histogram series from a TradingView chart by providing its unique id. Clean up unwanted overlays to declutter your analysis.

Instructions

Remove a custom line or histogram series by id.

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": {
      "id": "<id>"
    },
    "name": "chart_remove_series"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 20, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, but the description doesn't add context about what happens on removal (e.g., whether it's reversible, if it affects other series, or if it requires a chart to be open). The description is minimal and doesn't disclose any behavioral traits beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise and to the point. It front-loads the action and object. No wasted words, but it could be slightly more informative without becoming verbose.

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

Completeness2/5

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

Given the tool has one parameter, no output schema, and minimal annotations, the description is insufficient. It doesn't explain how to obtain the id, whether the series must be custom (as opposed to built-in), or any side effects. The context signals show low schema coverage, so the description should compensate but doesn't.

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?

The schema has one parameter 'id' with no description (0% coverage). The description mentions 'by id' but doesn't explain what the id refers to (e.g., the id from chart_add_series or chart_get_state). Since there's only one parameter and the description gives a hint, it's slightly above baseline but still lacks detail.

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 states the action (remove) and the resource (custom line or histogram series) identified by id. It distinguishes from sibling tools like chart_add_series and chart_remove_indicator by specifying 'custom line or histogram series'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It doesn't mention prerequisites like needing to add a series first or that it only applies to custom series, not built-in ones. Sibling tools like chart_remove_indicator and chart_remove_level exist, but no differentiation is provided.

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