Skip to main content
Glama
palewire

datawrapper-mcp

by palewire

export_chart_png

Read-onlyIdempotent

Export a Datawrapper chart as a PNG image. Supports high-resolution output via zoom parameter. Use only when the user explicitly requests to see the chart.

Instructions

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


Export a Datawrapper chart as PNG and display it inline. The chart must be created first using create_chart. Supports high-resolution output via the zoom parameter. IMPORTANT: Only use this tool when the user explicitly requests to see the chart image or export it as PNG. Do not automatically export charts after creation unless specifically asked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chart_idYesID of the chart to export
widthNoWidth of the image in pixels (optional)
heightNoHeight of the image in pixels (optional)
plainNoIf true, exports only the visualization without header/footer
zoomNoScale multiplier for resolution, e.g., 2 = 2x resolution
transparentNoIf true, exports with transparent background
border_widthNoMargin around visualization in pixels
border_colorNoColor of the border, e.g., '#FFFFFF' (optional)
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.
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, which are consistent. Description adds that it displays inline and supports high-res zoom, plus the explicit usage constraint. No contradictions.

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

Conciseness4/5

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

Description is reasonably concise but includes a warning header that might be considered clutter. Front-loaded with key constraints and purpose. Could be slightly tighter.

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?

No output schema, but description covers what the tool does (export PNG, inline display) and key parameter notes. It addresses prerequisite and usage constraints, making it fairly complete for a parameter-rich tool.

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 has 100% description coverage for all 9 parameters, so description adds little new. It only highlights zoom for high-res and plain for no header/footer, but that's not essential beyond schema.

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?

Clearly states it exports a chart as PNG and displays inline. Distinguishes from siblings like create_chart and get_chart by specifying the export action and dependency on prior creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use only on user request for chart image or PNG export, and warns against automatic export. Also notes prerequisite that chart must exist via create_chart.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/palewire/datawrapper-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server