Skip to main content
Glama

Delete several tasks

delete_tasks
DestructiveIdempotent

Delete up to 50 tasks in one call. ALWAYS list the tasks (title and day) and get the user's confirmation first, unless they explicitly asked to delete exactly these. One undo_last_change restores all of them.

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": {
      "ids": "<ids>"
    },
    "name": "delete_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds genuinely new behavior: the 50-per-call ceiling and the fact that a single undo_last_change restores the entire batch. That reversibility scope is exactly the fact an agent needs before committing a destructive bulk operation.

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, each doing distinct work: scope, mandatory confirmation workflow, recovery guarantee. The most safety-critical instruction is front-loaded after the one-line scope statement.

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 destructive single-parameter mutation with no output schema, it covers cap, confirmation, and undo semantics. Minor gaps remain: what happens on partially invalid ids, and how repeating-task occurrences are affected beyond the id format.

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 description coverage is reported as 0%, so the description must compensate; 'up to 50 tasks in one call' clarifies the cardinality of the ids array and the batching semantics rather than just naming the parameter. The per-id sourcing hint lives in the schema itself, and the description adds no detail on malformed or nonexistent ids.

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 ('Delete ... tasks') plus a concrete batch scope ('up to 50 tasks in one call'), which cleanly separates it from the singular delete_task sibling. No ambiguity about what the tool does.

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 an explicit precondition workflow — list titles/days and confirm with the user — plus the exception ('unless they explicitly asked to delete exactly these') and a recovery path via undo_last_change. It never explicitly says to use delete_task for a single task, so batch-vs-single routing is left to inference from the 50-item cap.

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