Skip to main content
Glama

Batch Delete Entries

batch_delete_entries
Destructive

Delete multiple journal entries in one transaction (up to 50 per batch) to remove outdated records, with optional permanent deletion and workspace or project scoping.

Instructions

Delete multiple existing journal entries in a single transaction. Max 50 per batch.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "batch_delete_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idsNo
permanentNo
workspace_idNoOptional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key.
project_numberNoOptional project number for workspace resolution.

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
countNo
errorNoHuman-readable error message
deletedNo
detailsNoAdditional error context
successNo
warningNo
categoryNoError category (validation, query, connection, internal)
notFoundNo
permanentNo
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv9.1.0
    • addedInput schema / properties / project_number
      Added value: +{
      +  "description": "Optional project number for workspace resolution.",
      +  "type": [
      +    "number",
      +    "string"
      +  ]
      +}
  2. First observedv9.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new behavior the annotations do not convey: atomicity ('single transaction') and a hard batch ceiling of 50. It omits important mutation semantics, though — whether the 'permanent' flag makes deletions irreversible or recoverable, and whether one invalid ID aborts the whole batch.

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 tight sentences with no filler; the core action is front-loaded and the batch limit is a useful constraint sentence that earns its place.

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

Completeness3/5

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

Return values need not be explained since an output schema exists, and annotations cover the danger profile. However, with four optional parameters (none required) the description leaves ambiguous what happens with an empty entry_ids list and what 'permanent' means, which is a real gap for a destructive batch tool.

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?

Schema coverage is only 50%: workspace_id and project_number are documented in the schema, but entry_ids and the destructive 'permanent' flag (default false) have no descriptions anywhere. The description names no parameters and never explains what 'permanent' changes, leaving the most consequential parameter undefined for a destructive operation.

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?

States a specific verb and resource ('Delete multiple existing journal entries') and adds the batching qualifier 'in a single transaction', which separates it from the single-entry delete_entry/team_delete_entry siblings. It stops short of naming an alternative tool or clarifying the team_ vs non-team_ pairing, so it is clear but not fully differentiated.

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: 'multiple ... in a single transaction' suggests using this instead of repeated single deletes, and 'existing' hints at a precondition. There is no explicit when-to-use/when-not guidance, no mention of when to prefer delete_entry, and no statement about soft vs hard deletion in relation to the 'permanent' flag.

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

Deploy Server

Other Tools