tradingview-mcp-server

screen_etf

Read-onlyIdempotent

Screen ETFs by performance and technical criteria, including moving averages and valuation filters, to return matching exchange-traded funds.

Instructions

Screen ETFs (Exchange-Traded Funds) based on performance and technical criteria. Returns ETFs matching the specified filters.

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

Input Schema

Name	Required	Description
`limit`	No	Number of results to return (1-200). Default: 20
`columns`	No	Optional: specific columns to include in results. If not provided, uses minimal default columns.
`filters`	No	Array of filter conditions to apply
`markets`	No	Markets to scan. Valid values: america, uk, germany, france, italy, spain, sweden, norway, denmark, finland, brazil, india, japan, hongkong, china, australia, canada, turkey, uae, and 30+ more. Default: ['america']
`sort_by`	No	Field to sort results by. Default: 'market_cap_basic'
`sort_order`	No	Sort order. Default: 'desc'

Output Schema

Name	Required	Description	Default
`etfs`	Yes
`metadata`	Yes
`total_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.7.0Aug 19, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / filters / items / additionalProperties
```
Added value: +false
```

changedInput schema / properties / filters / items / properties / value / description

Previous value: -"Value to compare against. Not required for 'empty' and 'not_empty' operators. Use number, string, or [min, max] array for in_range. For above_percent/below_percent, use [field_name, percent_number] e.g. ['SMA200', 10]."New value: +"Value to compare against. Empty and not_empty omit value. above_percent and below_percent use [field, percent]. has and has_none_of use a non-empty string array."

addedInput schema / properties / filters / items / properties / value / oneOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "items": {
+      "type": "number"
+    },
+    "maxItems": 2,
+    "minItems": 2,
+    "type": "array"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "maxItems": 2,
+    "minItems": 2,
+    "prefixItems": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      }
+    ],
+    "type": "array"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "etfs": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "metadata": {
+      "additionalProperties": false,
+      "properties": {
+        "cache_hit": {
+          "type": "boolean"
+        },
+        "missing_symbols": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "requested_count": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "retrieved_at": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "returned_count": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "source": {
+          "type": "string"
+        },
+        "unavailable_symbols": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "retrieved_at",
+        "source",
+        "cache_hit",
+        "requested_count",
+        "returned_count",
+        "missing_symbols"
+      ],
+      "type": "object"
+    },
+    "total_count": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total_count",
+    "etfs",
+    "metadata"
+  ],
+  "type": "object"
+}

First observedv0.0.0-devJul 13, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety expectations. The description adds only that the tool returns ETFs matching filters, which is basic behavior. No additional behavioral traits (e.g., pagination, rate limits, data ties) are disclosed, but with this tool's simple read-only nature, a 3 is appropriate.

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 concise sentences that immediately state the tool's purpose and return behavior. No filler or redundant details; it earns its place.

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

Completeness5/5

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

For a read-only screening tool with a fully documented input schema and an output schema present, the description is complete enough. It conveys the core purpose and result, while the schema covers parameter details and the output schema covers return structure.

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%, so the input schema already documents all parameter meanings and valid values. The description's phrase 'performance and technical criteria' provides a high-level hint but doesn't add details beyond the schema, so the baseline 3 applies.

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 clearly states the tool screens ETFs based on performance and technical criteria and returns matching ETFs. The verb 'Screen' and specific resource 'ETFs' make its purpose unambiguous, and it is naturally distinguished from sibling tools like screen_stocks and screen_forex by the asset class.

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 clearly identifies the context: use when screening ETFs. No explicit when-not or alternative tool references are given, but the ETF-specific scope makes usage obvious. It lacks direct mentions of when to prefer other screen_* tools, so it doesn't reach a 5.

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

Deploy Server