Skip to main content
Glama

List Saved Queries

list-saved-queries
Read-onlyIdempotent

Use when the user asks about their saved searches, wants to reuse a previous list, or needs query IDs for inclusion/exclusion filtering.

Returns saved queries with their domain arrays. Only returns queries with saved domains (count > 0). Filter by tags or action type to narrow results.

Available fields for the 'fields' parameter: query_id, query_name, action, user_name, mtime, domains, domain_count, persona_id_count, query_params, tags. Field details: https://docs.discolike.com.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-saved-queries"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOutput fields to include in response
formatNoResponse format: 'rows' or 'columnar'rows
contextNoWhy you are calling this tool, in a few words. No names or emails.
filtersNoInput filters for listing saved queries.
llm_modelNoYour model id, or "unknown".
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • addedOutput schema / properties
      Added value: +{
      +  "_mcp_instructions": {
      +    "description": "Server-issued metadata for this conversation.",
      +    "properties": {
      +      "conversation_id": {
      +        "description": "The server-issued conversation identifier.",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  }
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Why you are calling this tool, in a few words. No names or emails.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Your model id, or \"unknown\".",
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds real value with the filtering rule 'only returns queries with saved domains (count > 0)', which the agent could not infer elsewhere. It says nothing about pagination behavior or result ordering, leaving that to the schema.

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?

Front-loaded with the usage triggers, then scope, then the field enumeration, which is long but carries information absent from the schema. The docs URL is marginal padding, but no sentence is redundant with the structured fields.

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?

For a read-only list tool with a full-schema, an output schema, and full annotation coverage, the description supplies what structured data cannot: when to call it, the saved-domains-only constraint, and the field-name vocabulary. Pagination defaults and return shape are legitimately left to the schema, so nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100%, so a baseline of 3 applies. The description exceeds that by enumerating the exact valid values for the 'fields' array (query_id, query_name, action, domains, tags, etc.), which the schema only describes generically as 'Output fields to include in response'. It also clarifies that filters can be by tags or action type.

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

Purpose4/5

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

States a specific verb+resource (list / saved queries) plus a non-obvious scope restriction: only queries with saved domains (count > 0) are returned. That goes beyond the title. It does not explicitly distinguish itself from similarly-named siblings like list-tags or get-domains-by-tags, but the resource is distinct enough to avoid confusion.

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?

Names three concrete triggers: user asks about saved searches, wants to reuse a previous list, or needs query IDs for inclusion/exclusion filtering. This gives an agent clear entry conditions. It stops short of stating when NOT to use it or naming a specific alternative tool for the ID-lookup case, which is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources