TradingView Unified MCP

Overview Schema Source Related Servers Discussions Admin

job_submit

Start a bounded background sequence of fully specified tool calls. Arguments stay in process memory; no cookie, webhook, Pine or secret payload is written to a job database. Jobs do not resume automatically after restart.

Instructions

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": {
      "calls": "<calls>"
    },
    "name": "job_submit"
  }
}

Input Schema

Name	Required	Description	Default
`calls`	Yes
`stop_on_error`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 21, 2026

TDQS

B3.3/5.0

Behavior4/5

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

With annotations already declaring non-read-only, non-idempotent, non-destructive, the description still adds real context: the job is bounded, arguments live in process memory, no secrets/cookies/webhooks are persisted, and jobs do not auto-resume after restart. These are material traits an agent cannot get from the annotations.

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?

Three tight sentences, front-loaded with the core action, followed by the two constraints that matter. Nothing is padding.

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 tool that spawns an async job and has no output schema, the description omits the most operationally important fact: what it returns (presumably a job id) and how to track it via job_get/job_cancel/job_list. Behavioral constraints are well covered, but the follow-up contract is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and only the nested 'tool' field has any description; 'stop_on_error' has an empty description and the 'calls' array itself is undocumented. The description adds almost nothing about the parameters — 'bounded' loosely hints at maxItems but never mentions stop_on_error or argument shape.

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: start a bounded background sequence of tool calls. The word 'background' distinguishes it in spirit from the synchronous-sounding batch_execute, but it never names that sibling explicitly, so an agent must infer the split.

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?

There is no explicit when-to-use guidance or alternative named. The description implies a fit for pre-computed, non-interactive call sequences ('fully specified'), but it never says to prefer batch_execute for short synchronous work or job_get/job_cancel for follow-up, leaving selection to inference.

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

Deploy Server