Skip to main content
Glama
poddubnyoleg

Lightdash MCP Server

by poddubnyoleg

update-dashboard-filters

Update dashboard-level filters to add global date ranges, category filters, or change filter options that apply to all charts on the dashboard.

Instructions

Update dashboard-level filters that apply to all tiles.

Dashboard filters allow users to:

  • Filter all charts on a dashboard at once

  • Create interactive dashboards where users can change filters

  • Implement global date ranges or category filters

Filter configuration structure: Filters use the same structure as chart filters with:

  • Field references (fieldId)

  • Operators (equals, notEquals, contains, greaterThan, etc.)

  • Values or value ranges

  • Time-based filters (inThePast, inTheNext, etc.)

When to use:

  • To add global date range selectors

  • To create region/category filters that apply to all charts

  • To update filter options or defaults

  • To remove filters that are no longer needed

Important: Changes apply immediately to all dashboard viewers.

Testing: Use run-dashboard-chart after updating to verify filters work as expected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dashboard_nameYesName of the dashboard (supports partial matching)
filtersYesJSON string of filter configuration. Use same structure as chart filters. Example: {"dimensions": {"id": "root", "and": [{"id": "filter1", "target": {"fieldId": "table_field"}, "operator": "equals", "values": ["value"]}]}}
Behavior4/5

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

Discloses that changes apply immediately to all dashboard viewers, which is a critical behavioral trait. No annotations provided, so description carries this burden. It also recommends verification via run-dashboard-chart, implying no built-in validation.

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 clear sections (purpose, user benefits, filter structure, usage scenarios, important note, testing tip). Every sentence is informative and earns its place without unnecessary verbosity.

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?

For a tool with two parameters and no output schema, the description fully explains the input format and behavior. It covers the filter structure in detail and provides usage guidance, making it complete for agent invocation.

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 both parameters. The description adds value by explaining the filter configuration structure, listing supported operators and time-based filters, and providing an example JSON.

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 verb 'Update' and resource 'dashboard-level filters', and distinguishes from sibling tools like update-chart and update-dashboard-tile by focusing on filters that apply to all tiles.

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 specific scenarios (e.g., adding global date range selectors, creating region/category filters). It also suggests testing after update. It does not explicitly exclude chart-specific filter updates, but the context is clear.

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