Skip to main content
Glama

delete_saved_search

DestructiveIdempotent

Remove a saved search filter from Zotero permanently. This deletes only the stored filter, leaving items and citations intact.

Instructions

DESTRUCTIVE, but low-risk -- permanently deletes this saved search definition. Unlike delete_item_permanently/delete_collection, this doesn't touch any items or their citations -- a saved search is just a stored filter, not a container.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
Behavior5/5

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

Beyond annotations (destructiveHint=true), describes the nature of destruction: 'low-risk' and 'saved search is just a stored filter, not a container.' This adds contextual insight about what is affected (definition only, not items or citations), which is valuable behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with 'DESTRUCTIVE, but low-risk' and zero waste. Every phrase adds value, including the clarifying contrast with other destructive tools.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter delete tool with no output schema, the description is complete. It explains what is deleted, what is not, and the safety profile. Annotations cover idempotency and destructiveness, and the description adds the critical distinction from deleting containers.

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

Parameters2/5

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

The schema has one parameter 'key' with 0% description coverage. The tool description does not explain what 'key' refers to or how to obtain it. The only implicit link is the phrase 'saved search definition,' but it does not compensate for the missing parameter semantics.

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?

States explicitly 'permanently deletes this saved search definition' with a clear verb and resource. Differentiates from sibling tools by naming delete_item_permanently and delete_collection, making its scope unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit contrast with alternatives: 'Unlike delete_item_permanently/delete_collection, this doesn't touch any items or their citations.' This tells the agent exactly when this tool is appropriate and when it is not, satisfying the 'when/when-not/alternatives' criterion.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/herbertkokholm/cite-caddy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server