Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by madiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

alert_delete

Delete a specific alert by ID or remove all active alerts to manage your TradingView alert list.

Instructions

Delete a specific alert by id, or all active alerts

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

Input Schema

NameRequiredDescriptionDefault
alert_idNoAlert id to delete (from alert_list)
delete_allNoDelete all active alerts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does disclose the destructive scope ('specific alert' or 'all active alerts'), which is important, but it does not mention irreversibility, confirmation, or what happens if both parameters are supplied.

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, efficient sentence with no redundant content. The two deletion modes are front-loaded and immediately actionable.

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?

For a low-complexity delete tool with full schema coverage, the description names the operation and both modes. However, leaving ambiguous what happens if no parameters or both parameters are provided is a notable gap for an AI agent invoking 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%, and the schema already documents both parameters. The description adds the useful 'or' relationship between alert_id and delete_all and the 'active' qualifier, but it does not clarify mutual exclusivity, precedence, or behavior when neither parameter is provided.

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 states a specific verb ('Delete'), a clear resource (alert), and the two operational modes: by id or all active alerts. This distinguishes it clearly from siblings like alert_create and alert_list.

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 description implies when to use this tool—when an alert needs to be deleted—and distinguishes between deleting one specific alert versus all active alerts. However, it does not explicitly reference alternatives like alert_create or alert_list, nor does it state when not to use this tool.

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

Deploy Server

Other Tools