Skip to main content
Glama
Sign In
datawrapper-mcp

datawrapper-mcp

by palewire
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delete Chart

delete_chart
DestructiveIdempotent

Permanently remove a Datawrapper chart by its chart ID using the Datawrapper MCP server. Use this to clean up or discard charts no longer needed.

Instructions

⚠️ DATAWRAPPER MCP TOOL ⚠️ This is part of the Datawrapper MCP server integration.

Delete a Datawrapper chart permanently.

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": {
      "chart_id": "<chart_id>"
    },
    "name": "delete_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
chart_idYesID of the chart to delete
access_tokenNoOptional Datawrapper API token. When provided, uses the caller's account. When omitted, falls back to the server's DATAWRAPPER_ACCESS_TOKEN env var.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is largely covered by structured data. The description's 'permanently' usefully confirms irreversibility, but it says nothing about the effect on published charts, permission/ownership requirements, or failure behavior when the chart does not exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two lines of branded boilerplate ('⚠️ DATAWRAPPER MCP TOOL ⚠️' and the server-integration sentence) and a horizontal rule consume space without informing invocation, while the substantive content is a single short sentence. The useful content is present but is padded by non-earning decoration.

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?

An output schema exists, so return values need not be explained, and annotations cover the destructive/idempotent profile. What remains missing is impact context (e.g., whether deletion affects published charts or is recoverable, and error conditions), which matters for a destructive operation.

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% and both parameters (chart_id, access_token) are documented in the schema, so the description is not required to compensate. It adds no extra meaning about chart_id format or token fallback behavior beyond what the schema already states.

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?

The description states a specific verb and resource ('Delete a Datawrapper chart') and adds an important scope qualifier ('permanently'). It is clear what the tool does, but it does not distinguish itself from siblings like update_chart or publish_chart, which an agent must infer from names alone.

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 when-to-use guidance, no statement of prerequisites or alternatives (e.g., 'to modify instead of remove a chart, use update_chart'), and no exclusions. The agent is left to infer that this is the only deletion 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