Skip to main content
Glama
poddubnyoleg

Lightdash MCP Server

by poddubnyoleg

update-chart

Update a saved chart's configuration with partial updates for name, description, metrics, chart type, filters, sorts, and pivot settings.

Instructions

Update an existing saved chart's configuration.

This tool allows partial updates - you only need to provide the fields you want to change.

Updatable fields:

  • name: Chart name

  • description: Chart description

  • metric_query: JSON string with metricQuery updates (dimensions, metrics, filters, sorts, etc.)

  • chart_config: JSON string with chartConfig updates (visualization settings)

  • pivot_config: JSON string with pivotConfig updates

Common use cases:

  1. Change sorting: metric_query: {"sorts": [{"fieldId": "table_field_name", "descending": false}]}

  2. Update filters: metric_query: {"filters": {"dimensions": {"id": "root", "and": [...]}}}

  3. Change chart type: chart_config: {"type": "cartesian", "config": {...}}

  4. Add/remove dimensions or metrics: metric_query: {"dimensions": ["dim1", "dim2"], "metrics": ["metric1"]}

Important notes:

  • Uses PATCH endpoint - only provided fields are updated

  • For metric_query updates, provide only the keys you want to change

  • The tool merges your updates with the existing configuration

  • Use get-chart-details first to see current configuration

Example - Change sort to ascending by name:

chart_identifier: "My Chart Name"
metric_query: {"sorts": [{"fieldId": "table_column_name", "descending": false}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chart_identifierYesChart name (exact match) or UUID to update
nameNoOptional: New name for the chart
descriptionNoOptional: New description for the chart
metric_queryNoOptional: JSON string with metricQuery fields to update (e.g., sorts, filters, dimensions, metrics)
chart_configNoOptional: JSON string with chartConfig fields to update
pivot_configNoOptional: JSON string with pivotConfig to update. Use null to remove pivot.
Behavior4/5

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

With no annotations, the description discloses behavioral traits: it uses a PATCH endpoint, merges updates, and lists updatable fields. It also warns about JSON string parameters. It lacks details on error handling, rate limits, or permanence, but overall provides sufficient transparency for an agent to understand the tool's behavior.

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?

The description is well-structured with sections (purpose, updatable fields, common use cases, important notes, example) and uses markdown for readability. It is slightly verbose due to multiple examples, but every part earns its place for clarity. Front-loaded with the main purpose.

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?

Given the tool's complexity (6 parameters, partial updates, JSON inputs) and the absence of an output schema, the description covers usage patterns, merge behavior, and prerequisite steps. It is missing a description of the return value, but overall provides a complete understanding for an agent.

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

Parameters5/5

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

The input schema has 100% coverage, so baseline is 3. The description significantly adds value by providing concrete examples for each parameter (e.g., changing sorts, filters, chart type) and explaining how to use JSON strings. This exceeds the baseline and helps the agent understand parameter usage.

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 'Update an existing saved chart's configuration' using a specific verb and resource. It distinguishes from sibling tools like create-chart and delete-chart by specifying partial updates and listing common use cases that differentiate it from querying or read operations.

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 explains that the tool allows partial updates and provides common use cases and important notes, including recommending 'Use get-chart-details first to see current configuration.' However, it does not explicitly contrast with when to use alternative tools like run-chart-query for testing queries, leaving some ambiguity.

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/poddubnyoleg/lightdash_mcp'

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