Skip to main content
Glama

Delete a search (destructive)

delete_search
DestructiveIdempotent

Deletes a search with its leads and outreach; a running one is stopped first. Nothing is refunded and it cannot be undone. Ask the user to confirm and pass confirm=true. [REST: DELETE /api/tasks/{id}]

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": {
      "task_id": "<task_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes
task_idYesThe search id (task id), e.g. from list_searches or create_search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description still adds genuine context beyond them: cascade deletion of leads and outreach, the running-search stop, no refunds, and irreversibility. No return shape or error behavior is described, which keeps it at 3.

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?

Three short sentences, front-loaded with the action and scope, then consequences, then the required user-confirmation step. Every sentence carries distinct information; nothing is redundant.

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 two-parameter destructive tool with no output schema and full annotation coverage, this covers what an agent needs: what is destroyed, that it is irreversible, that a running search is stopped, and the confirmation requirement. No meaningful gap remains.

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

Parameters4/5

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

Schema coverage is 50%: task_id is documented in the schema, while confirm has no description there. The description compensates by explaining that confirm=true must be passed and tied to a real user confirmation, which is more than the bare const gives. It does not explain the task_id format, but the schema already does.

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 a specific verb and resource ("Deletes a search") and immediately scopes the blast radius: its leads and outreach go too, and a running search is stopped first. That distinguishes it from control_search (stop only) and edit/rename siblings without the agent needing to open another schema.

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 clear precondition: ask the user to confirm and pass confirm=true. "A running one is stopped first" implicitly tells the agent not to run a separate stop step beforehand, but the description never names an explicit alternative (e.g. control_search) for the non-destructive case, so the routing guidance stops just short of explicit.

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