Skip to main content
Glama

redash_query

Manage Redash queries: list, search, create, update, delete, run adhoc queries, and schedule or export results.

Instructions

Manage Redash queries. Actions: list, search, get, create, update, archive, delete, run, adhoc, export, schedule

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
idNoQuery ID (for get/update/archive/delete/run/export)
qNoSearch term (for search)
nameNoQuery name (for create)
queryNoSQL or MongoDB JSON query (for create/update/adhoc). For MongoDB, use JSON format e.g. {"collection": "my_col", "query": {"field": "value"}, "limit": 50, "sort": [{"name": "field", "direction": -1}]}
data_source_idNoData source ID
max_rowsNoMax rows to return for adhoc queries (default 200, prevents huge responses)
pageNo
page_sizeNoResults per page (default 10, max 250)
pathNoFile path to export results (for export). Supports .csv and .json
intervalNoSchedule interval in seconds (for schedule). e.g. 300=5min, 3600=1hr, 86400=daily
untilNoSchedule end datetime ISO format (for schedule, optional)
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as side effects of delete/archive, synchronous vs asynchronous run, authentication needs, or rate limits. The description is silent on these critical aspects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (two sentences) and front-loaded with the purpose. However, it is terse and could benefit from grouping or examples. Still, it is efficient with no wasted words.

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?

Given the tool's complexity (12 parameters, many actions, no output schema, no annotations), the description is incomplete. It does not explain return values, error handling, or action-specific behaviors like scheduling or exporting. Considerable gaps remain.

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 baseline is 3. The description adds some context for the query parameter (MongoDB JSON format) and max_rows (default, prevents huge responses) but overall adds minimal value beyond the schema. The main description only lists actions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Manage Redash queries' which is generic, and then lists actions. It conveys the general domain but lacks specificity about what the tool does as a whole. It does not differentiate from sibling tools like redash_alert or redash_dashboard.

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?

The description provides no guidance on when to use this tool versus alternatives. No when-not-to-use, prerequisites, or exclusions are mentioned. It merely lists possible actions without context.

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/wise-toddler/redash-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server