Skip to main content
Glama

batch_remove_items

Destructive

Removes a confirmed batch of tasks or projects by stable ID, validates the complete batch before deletion, and verifies each ID is absent afterward.

Instructions

Remove a user-confirmed set of tasks or projects by stable ID. The complete batch is validated before deletion and every ID is verified absent afterward.

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": {
      "items": "<items>"
    },
    "name": "batch_remove_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesConfirmed tasks or projects to remove. The complete batch is validated before deletion.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.18.0
    • changedInput schema / properties / items / description
      Previous value: -"Array of items (tasks or projects) to remove"New value: +"Confirmed tasks or projects to remove. The complete batch is validated before deletion."
    • changedInput schema / properties / items / items / properties / id / description
      Previous value: -"The ID of the task or project to remove"New value: +"Stable ID of the task or project to remove"
    • addedInput schema / properties / items / items / properties / id / minLength
      Added value: +1
    • removedInput schema / properties / items / items / properties / name
      Removed value: -{
      -  "description": "The name of the task or project to remove (as fallback if ID not provided)",
      -  "type": "string"
      -}
    • changedInput schema / properties / items / items / required
      Previous value: -[
      -  "itemType"
      -]New value: +[
      +  "id",
      +  "itemType"
      +]
    • addedInput schema / properties / items / maxItems
      Added value: +100
    • addedInput schema / properties / items / minItems
      Added value: +1
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true, but the description adds valuable behavioral context: the batch is validated before deletion and every ID is verified absent afterward, which is not captured by annotations alone.

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 with no wasted words. The key information is front-loaded in the first sentence.

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 batch operation with validation, the description adequately covers pre- and post-conditions. No output schema exists, so it's complete enough.

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%, so baseline is 3. The description adds minimal extra meaning beyond the schema, such as 'stable ID' and 'user-confirmed set', but these are largely redundant.

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?

The description clearly states it removes a batch of tasks or projects by stable ID, using specific verb 'Remove' and resource 'tasks or projects'. It distinguishes from the sibling 'remove_item' which presumably removes a single item.

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

Usage Guidelines2/5

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

The description does not mention when to use this tool vs alternatives like 'remove_item' or 'batch_move_tasks'. No explicit context or exclusions are provided.

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