Skip to main content
Glama
poddubnyoleg

Lightdash MCP Server

by poddubnyoleg

update-dashboard-tile

Update dashboard tile properties: position, size, title, content, or chart displayed, using a 36-column grid for layout.

Instructions

Update any properties of a tile on a dashboard.

You can modify multiple tile properties in a single operation:

Position properties (at tile level):

  • x, y: Change tile position

  • h, w: Resize tile

Display properties (in properties object):

  • title: Change display name

  • content: Update markdown content

  • savedChartUuid: Change which chart is displayed (for saved_chart tiles)

  • Any other tile-specific properties

CRITICAL - Grid System: Lightdash uses a 36-column grid horizontally:

  • For 2 tiles per row: w: 18 each (x: 0 and x: 18)

  • For 3 tiles per row: w: 12 each (x: 0, x: 12, x: 24)

  • For full-width tile: w: 36

When to use:

  • To reposition or resize tiles on a dashboard

  • To update multiple tile properties at once

  • To change content of markdown tiles

  • To swap which chart is displayed in a chart tile

Example properties_update values:

  • Two tiles per row: {"x": 0, "y": 0, "h": 6, "w": 18} and {"x": 18, "y": 0, "h": 6, "w": 18}

  • Full width: {"x": 0, "w": 36, "h": 6}

  • Reposition: {"x": 0, "y": 10}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dashboard_nameYesName of the dashboard (supports partial matching)
tile_identifierYesCurrent title of the tile or partial match to identify which tile to update
properties_updateYesJSON object string of properties to update. Position properties (x, y, h, w) go at tile level. Other properties go in properties object. Example: {"x": 0, "y": 5, "title": "New Title", "w": 12}
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the 36-column grid system, ability to modify multiple properties in one operation, and separates position vs display properties. It does not mention permissions or reversibility but adds substantial context beyond schema.

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 sections, bullet points, and examples. Front-loaded with main purpose. Some redundancy (repeats example values) but overall efficient and each sentence adds value.

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

Completeness3/5

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

No output schema, so description should explain return values or effects. It doesn't mention response or confirmation of update. It covers usage and parameters well but lacks output/confirmation info, making it slightly incomplete for an agent expecting feedback.

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?

Schema coverage is 100%, but description adds critical meaning: explains grid system for positioning, provides multiple examples for properties_update, clarifies structure (position at tile level, display in properties object). This significantly enriches 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 updates tile properties, lists specific properties (position, display), and distinguishes from sibling tools like rename-dashboard-tile. It uses specific verbs and identifies the resource (tile on dashboard).

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 explicitly lists scenarios like repositioning, resizing, updating multiple properties, and swapping charts. It provides clear context but does not explicitly mention when not to use or name alternative tools, though inference is possible.

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