Redash MCP Server

create_widget

Create a widget on a Redash dashboard with specified width and optional visualization or text content.

Instructions

Create a new widget on a dashboard

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>",
      "width": "<width>"
    },
    "name": "create_widget"
  }
}

Input Schema

Name	Required	Description
`text`	No	Text content for text widgets
`width`	Yes	Width of the widget (1-6)
`options`	No	Widget options
`position`	No
`dashboard_id`	Yes	ID of the dashboard to add the widget to
`visualization_id`	No	ID of the visualization to display (optional if text widget)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.1Jul 6, 2026

addedInput schema / properties / options / additionalProperties
```
Added value: +true
```

addedInput schema / properties / position

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "autoHeight": {
+      "description": "Whether the widget height should auto-grow",
+      "type": "boolean"
+    },
+    "col": {
+      "description": "Grid column, starting at 0",
+      "maximum": 11,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "row": {
+      "description": "Grid row, starting at 0",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "sizeX": {
+      "description": "Widget width in grid columns",
+      "maximum": 12,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "sizeY": {
+      "description": "Widget height in grid rows",
+      "maximum": 1000,
+      "minimum": 2,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedv0.0.13May 4, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, and the description fails to disclose behavioral traits such as required permissions, side effects, or return value. The minimal statement does not add transparency beyond the obvious.

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 a single concise sentence without superfluous content, front-loading the core purpose effectively.

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

Completeness2/5

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

With 6 parameters, nested objects (position, options), and no output schema, the description is too minimal. It fails to explain widget types, the role of visualization_id, or how it relates to dashboard layout.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high (83%), so the schema already documents parameters adequately. The description adds no extra meaning beyond what the schema provides.

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 action ('Create') and the resource ('new widget on a dashboard'). It is specific and distinct from sibling tools like delete_widget or update_widget.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The context is implied but lacks explicit guidance.

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

Deploy Server