Skip to main content
Glama

Delete a saved search

delete_saved_search
DestructiveIdempotent

Use this when the user wants a saved search removed for good. It cannot be restored. Searches already run and people already saved to lists are not affected. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "savedSearchId": "<savedSearchId>"
    },
    "name": "delete_saved_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
savedSearchIdYesThe saved search's id.

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 destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description still adds real value beyond them by stating the deletion is irreversible and by scoping the blast radius (previously run searches and people already on lists are unaffected), which an agent could not infer from the annotations. The trailing 'Free' is a cost signal but is too terse to be genuinely informative.

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?

Four short sentences, front-loaded with the trigger condition and immediately followed by the irreversibility warning, which is the right ordering. 'Free.' is an unexplained fragment that costs a beat of clarity without earning its place.

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 single-parameter destructive delete with no output schema, the definition covers the essentials: what it does, that it cannot be undone, and what collateral effects it does not have. Only the opaque 'Free' term and the absence of any pointer to the update/read siblings leave minor gaps.

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 100% and the single parameter carries its own description plus a strict hex/length pattern, so the schema does the work. The description adds no format, sourcing, or lookup guidance for savedSearchId, making the baseline 3 correct.

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?

The description states a specific verb and resource: removing a saved search 'for good.' It is clearly distinct from read-oriented siblings like get_saved_search or list_saved_searches, though it does not name update_saved_search as the non-destructive counterpart, leaving that distinction to inference.

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?

The trigger condition is explicit ('when the user wants a saved search removed for good'), which is exactly the when-to-use context an agent needs. It stops short of naming an alternative tool or an explicit when-not-to-use case, so it is clear context without 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