Skip to main content
Glama

List saved search criteria

listSearchPresets
Read-onlyIdempotent

List the criteria presets your team saved in People Search, newest first, each with its name and criteria. Reuse a preset's criteria when the user asks for a search like one they ran before.

Clera privately records this tool's inputs and results for usage tracking and support.

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": "listSearchPresets"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.

Output Schema

NameRequiredDescriptionDefault
presetsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds ordering (newest first), the contents of each item, and an unusual disclosure that inputs and results are recorded for usage tracking and support — genuinely new behavioral context. It stops short of describing pagination or limits on result size.

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 short, front-loaded paragraphs: purpose and contents first, then the reuse trigger, then the tracking note as a separate block. Nothing is redundant, though the tracking sentence is boilerplate that does not help tool selection.

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 simple read-only list with one optional parameter, an output schema, and rich annotations, the description covers what it returns, in what order, and when to reach for it. Only a pointer to sibling alternatives is missing.

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?

Single optional orgId parameter with 100% schema description coverage, which already explains 'Only needed when you belong to more than one organization.' The description adds no further meaning, so the baseline 3 applies.

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?

Specific verb and resource: 'List the criteria presets your team saved in People Search', plus ordering ('newest first') and return shape ('each with its name and criteria'). It implicitly separates itself from listSavedJobs and the search tools by naming the People Search preset domain, though it never names a sibling explicitly.

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?

Gives a concrete trigger: 'Reuse a preset's criteria when the user asks for a search like one they ran before.' That is a clear when-to-use, but there is no when-not guidance and no named alternative (e.g., run a fresh searchCandidates call instead).

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