Skip to main content
Glama
Sign In
TradingView Unified MCP

TradingView Unified MCP

by daviddme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

watchlist_export

Read-only

Export exact watchlist entries/section order as JSON or CSV through the safe local artifact store. No account session state is read or exported.

Instructions

Export exact watchlist entries/section order as JSON or CSV through the safe local artifact store. No account session state is read or exported.

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": {
      "watchlist_id": "<watchlist_id>"
    },
    "name": "watchlist_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNojson
target_idNoExact Chrome tab target ID from browser_list_tabs. Required for changes.
watchlist_idYesExact custom watchlist ID from watchlist_list; names are not IDs.
expected_layout_idNoExpected 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.8/5.0
Behavior4/5

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

Annotations already cover read-only and non-destructive, and the description adds real value on top: it clarifies that output lands in a local artifact store rather than mutating chart state, and that no account session state is read or exported (a privacy boundary an agent would otherwise not know). It still does not say where the artifact lands or what identifier is returned.

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?

Two short sentences, front-loaded with the action and scope, followed by the safety boundary. No filler and nothing that could be cut.

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?

With no output schema, the description should say more about what is produced; naming the artifact store partially covers this but not the artifact path/handle or whether a job id is returned. For a simple read-only export it is otherwise sufficient.

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 description covers format (JSON or CSV) and implies the watchlist_id scope, but says nothing about target_id or expected_layout_id, whose semantics live only in the schema. With 75% schema coverage that schema carries most of the load, so baseline 3 applies.

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+resource (export watchlist entries/section order) plus the output formats, which clearly separates it from watchlist_get, watchlist_list and the mutation siblings. It does not name any sibling explicitly, so differentiation is inferential rather than stated.

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?

'Export ... through the safe local artifact store' implies the use case (you want a file artifact rather than live state), but there is no explicit when-to-use/when-not or comparison against watchlist_get or watchlist_import_preview. The agent must infer that this is the artifact-producing path.

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