preset-mcp

enable_embedded_dashboard

Enable embedding for a dashboard and retrieve its embed UUID, specifying allowed domains for external embedding via Superset SDK.

Instructions

Enable embedding for a dashboard and return its embed UUID.

The returned UUID is used to embed the dashboard in external applications via the Superset embedded SDK.

Args: dashboard_id: The dashboard ID to enable embedding for. allowed_domains: List of domains allowed to embed (e.g. '["app.example.com"]'). Pass an empty list to allow all origins. dry_run: If True, preview the action without executing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dashboard_id": "<dashboard_id>"
    },
    "name": "enable_embedded_dashboard"
  }
}

Input Schema

Name	Required	Description	Default
`dashboard_id`	Yes
`allowed_domains`	No
`dry_run`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.2Jun 8, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It mentions that the tool enables embedding and returns a UUID, and that dry_run previews without executing. However, it does not clarify whether re-enabling an already embedded dashboard returns the same UUID, or discuss required permissions or side effects.

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 concise and well-structured, with a clear header sentence followed by an Args section. Every sentence adds value without redundancy. It is appropriately sized for the tool's simplicity.

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?

Given the output schema exists (not shown), the description covers the key return value (embed UUID) and links to SDK usage. However, it does not address edge cases like re-enabling or error conditions, which would enhance completeness for a 3-parameter action tool.

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 description coverage is 0%, so the description fully compensates. It explains each parameter: dashboard_id (required), allowed_domains (with example and behavior for empty list), and dry_run (previews action). This adds significant meaning beyond the raw 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's purpose: 'Enable embedding for a dashboard and return its embed UUID.' It specifies the action (enable) and resource (dashboard), and distinguishes itself from sibling tools like disable_embedded_dashboard and get_embedded_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 description explains the use case: embedding dashboards via the Superset embedded SDK using the returned UUID. It does not explicitly mention when not to use this tool, but the context from sibling tools makes it clear. The inclusion of dry_run provides guidance on previewing the action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server