Skip to main content
Glama
poddubnyoleg

Lightdash MCP Server

by poddubnyoleg

create-dashboard

Create a new dashboard in Lightdash to organize and display data, optionally adding tiles and tabs for structured layouts.

Instructions

Create a new dashboard in the Lightdash project.

You can create an empty dashboard (just name and description) or a fully configured dashboard with tiles and tabs.

Tile Types:

  • saved_chart: Display a saved chart (requires savedChartUuid in properties)

  • markdown: Text/markdown content (requires title and content in properties)

  • loom: Embedded Loom video (requires url in properties)

Tile Position Properties (required for each tile):

  • x: Column position (0-indexed, grid is 12 columns wide)

  • y: Row position (0-indexed)

  • h: Height in grid units

  • w: Width in grid units (max 12)

When to use:

  • To create a new empty dashboard that you'll populate later

  • To create a fully configured dashboard from a template or copy

  • Use duplicate-dashboard if you want to copy an existing dashboard

Best practice: Start with an empty dashboard, then use create-dashboard-tile to add content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the dashboard (must be unique within the project)
descriptionNoOptional: Description explaining the purpose of this dashboard
tilesNoOptional: JSON string array of tiles to add to the dashboard. Each tile needs type, properties with x/y/h/w positioning. Example: [{"uuid": "uuid1", "type": "markdown", "properties": {"title": "Welcome", "content": "# Hello"}, "x": 0, "y": 0, "h": 4, "w": 12}]
tabsNoOptional: JSON string array of tabs for organizing tiles. Example: [{"uuid": "tab-uuid", "name": "Overview", "order": 0}]
Behavior3/5

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

No annotations provided, so description must cover behavioral traits. It explains tile types and positioning but lacks details on idempotency, return value, error handling for duplicate names, or required permissions. Adequate but not comprehensive.

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?

Well-structured with clear sections, bullet points, and separate usage guidelines. While slightly lengthy, every sentence adds meaningful information. No unnecessary 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?

No output schema exists, yet description does not specify return value or confirmation of creation. However, for a creation tool with 4 parameters and clear schema, the description covers creation process and use cases sufficiently. Minor gap on output.

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% with descriptions for each parameter. The description adds extra value by detailing tile types, properties structure, and positioning, which enriches understanding beyond the 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?

The description clearly states the tool creates a new dashboard, and distinguishes from siblings like duplicate-dashboard and create-dashboard-tile. It specifies the ability to create empty or fully configured dashboards.

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?

Explicit 'When to use' section lists three scenarios and references alternative tool (duplicate-dashboard). Best practice recommendation to start empty and use create-dashboard-tile provides further guidance.

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