Datadog
saved_queries
Manage your personal library of reusable SELECT queries. action=save stores a query by name; action=run executes a saved query; action=list returns all your saved queries; action=delete removes one. [BUILD tier]
Remote thinair/data
Other tools also called saved_queries?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Query ID (alternative to name for run/delete)"
},
"sql": {
"type": "string",
"description": "SQL to store (required for action=save)"
},
"tag": {
"type": "string",
"description": "Filter by tag (action=list)"
},
"name": {
"type": "string",
"description": "Query name (save/run/delete)"
},
"tags": {
"type": "array",
"items": {
"type": "string"
},
"description": "Tags (action=save)"
},
"action": {
"enum": [
"save",
"run",
"list",
"delete"
],
"type": "string",
"description": "save | run | list | delete"
},
"connection": {
"type": "string",
"description": "Target connection name from this tenant's inventory. Call `list_connections` to see every name + dialect, then match semantically to the user's intent (e.g. 'analytics' → a connection named `*-analytics-*`; 'prod' → a connection with `prod-` prefix). If the user didn't specify, use the tenant's default (first added). Do not invent names — resolve from `list_connections` output."
},
"description": {
"type": "string",
"description": "Freeform description (action=save)"
}
}
}