Skip to main content
Glama
poddubnyoleg

Lightdash MCP Server

by poddubnyoleg

create-dashboard-tile

Add a new chart, markdown text, or embedded video tile to an existing dashboard with custom positioning.

Instructions

Create a new tile and add it to an existing dashboard.

Required for all tiles:

  • Position and size: x, y, h, w (in the properties JSON)

  • Tile type: One of 'saved_chart', 'markdown', 'loom'

Tile-specific requirements:

saved_chart tiles:

  • savedChartUuid: UUID of the chart to display (use list-charts to find)

  • Optional: title to override the chart's name

markdown tiles:

  • title: Display title

  • content: Markdown content to display

loom tiles:

  • url: Loom video URL

  • Optional: title

CRITICAL - Grid system:

  • Dashboard is 36 columns wide (not 12!)

  • x ranges from 0-35 (column position)

  • y is row position (grows downward)

  • w is width in columns (1-36)

  • h is height in grid units

  • For 2 tiles per row: use w: 18 each

  • For 3 tiles per row: use w: 12 each

  • For full width: use w: 36

When to use:

  • To add charts to a dashboard

  • To add markdown documentation/headers

  • To embed Loom videos for context

Best practice: Use get-dashboard-tiles first to see existing layout and find an empty position.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dashboard_nameYesName of the dashboard (supports partial matching)
tile_typeYesType of tile: 'saved_chart' (for charts), 'markdown' (for text), or 'loom' (for videos)
propertiesYesJSON object string with tile properties. MUST include x, y, h, w for positioning. Example for chart: {"x": 0, "y": 0, "h": 6, "w": 18, "savedChartUuid": "uuid-here"}
tab_uuidNoOptional: UUID of the tab to add the tile to. Leave empty to use the first tab (or no tab if dashboard has no tabs).
Behavior4/5

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

With no annotations, the description fully covers behavior: details the grid system (36 columns), tile-specific required fields, and positioning. It does not mention side effects like overwriting, but creation is inherently non-destructive.

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 and examples, but slightly verbose. Every sentence adds value, and critical information (grid system) is highlighted.

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 the complexity of multiple tile types and no output schema, the description thoroughly explains all necessary details for correct invocation, including parameter usage and best practices.

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 description adds significant value beyond the schema, detailing tile-specific properties for each type (saved_chart, markdown, loom) and the grid system. Schema coverage is 100%, but the description provides execution-critical examples and constraints.

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 tile and adds it to an existing dashboard, with explicit tile types and their requirements. It distinguishes from siblings like 'create-chart' and 'delete-dashboard-tile' by focusing on tile creation.

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 three specific use cases, and the best practice to first retrieve existing tiles provides context. However, it does not explicitly exclude alternatives or compare to siblings like 'update-dashboard-tile'.

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