Skip to main content
Glama
Sign In
Redash MCP Server

Redash MCP Server

by suthio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

remove_dashboard_favorite

Remove a dashboard from your favorites list by providing its ID. Manage which dashboards are bookmarked for easy access.

Instructions

Remove a dashboard from favorites

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": {
      "dashboardId": "<dashboardId>"
    },
    "name": "remove_dashboard_favorite"
  }
}

Input Schema

NameRequiredDescriptionDefault
dashboardIdYesID of the dashboard to remove from favorites

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.13

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only restates the action without additional details like side effects, permissions, or reversibility.

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?

One short sentence, no wasted words, front-loaded with the verb and noun.

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?

For a simple tool with one parameter and no output schema, the description is adequate but lacks usage and behavioral context.

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 coverage is 100% and the parameter description already says 'ID of the dashboard to remove from favorites'. The description adds no new meaning.

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 (remove) and the resource (dashboard from favorites), distinguishing it from siblings like add_dashboard_favorite (add) and remove_query_favorite (different resource).

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives (e.g., archive_dashboard). No prerequisites, context, or exclusions mentioned.

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

Deploy Server

Other Tools