Skip to main content
Glama
poddubnyoleg

Lightdash MCP Server

by poddubnyoleg

duplicate-dashboard

Copy an existing dashboard with all tiles, tabs, and filters to create a new dashboard under a different name. Useful for creating variants or test versions.

Instructions

Create a complete copy of an existing dashboard with a new name.

This copies everything from the source dashboard:

  • All tiles with their positions and configurations

  • All tabs (if the dashboard has tabs)

  • Dashboard-level filters

  • Layout and styling

What gets regenerated:

  • Dashboard UUID (new unique ID)

  • Tile UUIDs (new IDs for each tile)

  • Tab UUIDs (new IDs for each tab)

What stays the same:

  • Chart references (tiles still point to the same charts)

  • Content and configuration

  • Layout and positioning

When to use:

  • To create dashboard variants for different teams/regions

  • To create a test version before modifying production dashboards

  • To use an existing dashboard as a template

  • To create regional/customer-specific versions

Best practice: Use descriptive names to distinguish the copy from the original.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_dashboard_nameYesName of the dashboard to copy (supports partial matching)
new_dashboard_nameYesName for the new dashboard copy. Must be unique in the project.
new_descriptionNoOptional: Description for the new dashboard. If omitted, copies the source dashboard's description.
Behavior5/5

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

With no annotations, the description carries the full burden. It explicitly lists what gets copied (tiles, tabs, filters, layout), what gets regenerated (UUIDs), and what stays the same (chart references). This is comprehensive for a duplicate operation.

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 well-structured with sections and bullet points. Every sentence adds value. The core purpose is front-loaded immediately. No wasted words for a tool of this complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description adequately explains the behavior (complete copy, UUID regeneration, chart references preserved). It includes all necessary context for an agent to use the tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by explaining 'partial matching' for source_dashboard_name and uniqueness requirement for new_dashboard_name, which go beyond the schema descriptions.

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 uses the specific verb 'Create a complete copy of' and identifies the resource as an 'existing dashboard with a new name'. It clearly distinguishes from 'create-dashboard' by emphasizing copying rather than creation from scratch.

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 'When to use' section lists four concrete scenarios (e.g., creating variants, test versions). It implicitly suggests when not to use (e.g., when creating from scratch, use create-dashboard). Could be improved by explicitly naming alternatives.

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