Cloudera Data Visualization MCP Server

delete_visual

Delete a visual or dashboard by numeric ID. Removing a dashboard also deletes all linked chart visuals.

Instructions

Delete a CDV visual or dashboard by its numeric ID.

WARNING — CASCADE DELETION: Deleting a dashboard (type="dashboard") also permanently deletes ALL chart visuals linked to it as widgets. If you need to preserve the chart visuals, note their IDs before deleting the dashboard.

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": {
      "object_id": "<object_id>"
    },
    "name": "delete_visual"
  }
}

Input Schema

Name	Required	Description	Default
`object_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 26, 2026

TDQS

A4/5.0

Behavior4/5

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

The description explicitly warns about cascade deletion when deleting a dashboard, which is critical behavioral information. Since no annotations are provided, the description carries the transparency burden and does so effectively, though it does not mention other aspects like reversibility or permissions.

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 concise, with three sentences covering the main action and a critical warning. It is front-loaded with the primary purpose and every sentence adds value without redundancy.

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?

The description covers the core functionality and the crucial cascade behavior. However, it omits explanation of what 'CDV' stands for, how the tool determines the type (visual vs. dashboard) from the ID, and any details about the output schema. Despite this, the key nuance is addressed.

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 0% schema description coverage, the description must compensate. It identifies the parameter as a 'numeric ID' but does not explain how to differentiate between visual and dashboard IDs or provide additional format details. This adds some meaning but not comprehensive guidance.

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 action ('Delete') and the resource ('CDV visual or dashboard') with a specific method ('by its numeric ID'). This distinguishes it from sibling delete tools that target other resources like connections or datasets.

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 usage for deleting visuals or dashboards but does not explicitly state when to use this tool versus other deletion tools. The cascade warning provides context but no direct comparison to alternatives.

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

Deploy Server