Skip to main content
Glama

PickedJobs

Delete saved search

delete_saved_search
DestructiveIdempotent

Deletes one of this account’s saved searches and stops its email alerts. Does not use the job allowance.

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": {
      "id": "<id>"
    },
    "name": "delete_saved_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA saved search id from this account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds two things they do not cover: that deletion also cancels the search's email alerts, and that the call consumes no job allowance. It still does not state whether the deletion is permanent or recoverable.

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 short sentences with no filler. The primary action is front-loaded, followed by the two secondary facts an agent needs (alert cancellation, no quota cost).

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 delete with full annotation coverage and no output schema, the description supplies the key extras: side effect on alerts and quota exemption. The only meaningful omission is whether the deletion is irreversible or whether the record can be restored.

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 `id` parameter is fully documented as a UUID from this account, so the schema does the heavy lifting. The description adds no format or sourcing detail beyond what the schema already provides, which is the baseline 3 case for one fully-described parameter.

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 ('Deletes one of this account's saved searches') and adds the observable side effect of stopping email alerts. It is clearly distinguishable from siblings like list_saved_searches and save_search by its delete verb, though it does not name those alternatives in the text.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool to remove an existing saved search. There is no explicit when-to-use versus when-not-to-use guidance or pointer to the list tool for obtaining an id. The quota note ('Does not use the job allowance') gives useful cost context but is not usage routing.

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