From 256f1ea2d9f357d3b2e0bcf4aa65a898e8af170f Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Sat, 11 Jul 2026 00:43:29 +0000 Subject: [PATCH] docs: document resolve_url MCP/AI agent tool --- references/integrations/lightdash-mcp.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/references/integrations/lightdash-mcp.mdx b/references/integrations/lightdash-mcp.mdx index 629753db..d094adc9 100644 --- a/references/integrations/lightdash-mcp.mdx +++ b/references/integrations/lightdash-mcp.mdx @@ -359,6 +359,15 @@ MCP provides AI assistants with powerful tools to interact with your Lightdash d - **Find content** - Search for existing spaces, charts, and dashboards by name or description. Results include space breadcrumbs and direct links. Optionally scope the search to a single space (and its descendants) by passing a space slug. - **List content** - Browse accessible content as a hierarchy. By default it returns root-level spaces; pass a space slug to list the charts, dashboards, and nested spaces directly inside that space. Use this when you want the agent to walk space → content rather than search by keyword. - **List verified content** - Discover charts and dashboards that admins have marked as verified, so agents can reference trusted, canonical patterns when building new content. If you want your agent to prefer verified patterns, ask it to in your prompt (e.g. _"Use verified charts as the reference for any new chart you build."_). +- **Resolve URL** (`resolve_url`) - Expand a Lightdash share link (`/share/`) into the full destination URL so the agent can read the project, chart, dashboard, or explore identifiers from the path and act on them. Use this when a user pastes a `/share/...` link into a chat — the tool only follows the redirect, so pair it with `read_content` (or any other read tool) to fetch the underlying content. Access is enforced through the same sharing permissions as the Lightdash app, so an agent can only expand links the current user can see. Non-share Lightdash URLs (e.g. `/projects//saved/`) don't need to be resolved — the agent can read identifiers from the path directly — and foreign-host URLs return an error. + + ```text + # A user pastes: + https://.lightdash.cloud/share/aBcD1234ecomXyZ + + # resolve_url returns the full URL, e.g.: + https://.lightdash.cloud/projects//dashboards//view + ``` #### Query execution