Skip to main content
Glama

List saved searches

list_saved_searches
Read-only

Use this when the user asks which searches are saved, or to find a saved search's id. Returns the organization's saved searches, people and company alike, or one kind with type. Free.

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_searches"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly saved searches of this kind.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, destructiveHint false and openWorldHint false, so the safety profile is covered. The description adds two things the annotations do not: the result scope is the whole organization, and the call is free (no quota cost), which matters for an agent choosing between calls. It omits any pagination or result-size behavior, which keeps this below a 5.

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?

Two sentences, usage guidance front-loaded, nothing padded. The trailing single-word 'Free.' is clipped but it earns its place as a cost signal.

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 one-optional-parameter read tool with annotations and no output schema, the description covers purpose, trigger, result scope, filtering, and cost. Only result volume or pagination behavior is left unstated, a minor gap at this complexity.

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 single enum parameter is fully documented in the schema, so the baseline is 3. The phrase 'or one kind with type' only restates that the type filter narrows to people or company without adding format or edge-case detail.

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 gives a specific verb and resource (list saved searches) and states the scope: the organization's saved searches, both people and company kinds. It also names a concrete secondary use case (finding a saved search's id), which separates it from get_saved_search, which retrieves a single search.

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?

It opens with an explicit when-to-use clause: the user asks which searches are saved, or needs a saved search's id. It does not name an alternative tool or state when not to use it, so it stops short of full routing guidance.

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