Skip to main content
Glama
Sign In
TradingView Unified MCP

TradingView Unified MCP

by daviddme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

watchlist_create

Create an independent named custom watchlist; verify its new ID, exact entries/order and account listing. Uses durable idempotency and refuses duplicate names.

Instructions

Create an independent named custom watchlist; verify its new ID, exact entries/order and account listing. Uses durable idempotency and refuses duplicate names.

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": {
      "name": "<name>",
      "idempotency_key": "<idempotency_key>",
      "target_id": "<target_id>",
      "expected_layout_id": "<expected_layout_id>"
    },
    "name": "watchlist_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNew custom watchlist name
entriesNo
target_idYesExact Chrome tab target ID from browser_list_tabs. Required for changes.
timeout_msNo
idempotency_keyYesUnique durable request key. Reuse only to reconcile the same request.
expected_layout_idYesExpected saved-layout ID. A mismatch stops the operation before writing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Adds real behavior beyond annotations: duplicate names are rejected, requests are guarded by durable idempotency, and the tool verifies new ID, entry order and account listing after writing. There is mild tension with idempotentHint=false, but that hint refers to natural idempotence while the key-based dedupe is described consistently with the schema's 'reuse only to reconcile the same request'.

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?

One compact sentence, front-loaded with the primary action and followed by the guarantee/side-effect clauses. No filler, though the semicolon chain packs three distinct ideas together and could be split for scanability.

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 mutating, open-world tool with no output schema, the description covers the write, the idempotency contract, the duplicate-name rejection and the post-write verification. It stops short of stating the tab/session prerequisite implied by target_id, which is the main remaining gap.

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?

With 67% schema description coverage, the schema already explains name, entries format, target_id and expected_layout_id; the description adds only the implicit linkage of the idempotency key and the exact-order expectation for entries. The timeout_ms parameter is undocumented in both places and no parameter is named directly.

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?

States a specific verb and resource ('Create an independent named custom watchlist') plus the post-creation verification scope. The word 'independent' implicitly separates it from watchlist_add / watchlist_add_bulk, but no sibling is named explicitly.

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?

'Refuses duplicate names' and the idempotency requirement imply when the call will fail, giving some usage signal. However, it never tells the agent when to choose watchlist_create versus watchlist_import or watchlist_add, nor what prerequisites (an active tab from browser_list_tabs) are needed first.

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