Skip to main content
Glama

deletion_status

Read-onlyIdempotent

Check a batch of deletions, by its id: one you asked for with request_deletions, or one a held delete call returned. Pass waitSeconds (up to 50) to wait while it is pending or running.

Instructions

Check a batch of deletions, by its id: one you asked for with request_deletions, or one a held delete call returned. Pass waitSeconds (up to 50) to wait while it is pending or running. state is pending, expired, denied, running or done; each item's state is deleted, skipped (gone or changed since you asked), failed, not_approved or denied, and its outcome says why. message says what to do next.

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": {
      "batchId": "<batchId>"
    },
    "name": "deletion_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
batchIdYesThe batch id request_deletions or the held delete returned
waitSecondsNoSeconds to wait while the batch is pending or running, 0 to 50. Default 0: answer at once

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered; the description adds real value beyond that by disclosing the batch-level state vocabulary (pending/expired/denied/running/done), the per-item states and that 'skipped' means gone or changed since the request, and that message carries next actions. It does not discuss polling cost or rate limits, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and the id sources, then the wait behavior, then the state vocabulary the caller must interpret. It is a single dense paragraph and the state/outcome enumeration is justified, though the sentence listing five states followed by five item states is slightly compressed and harder to scan than a short list would be.

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?

With no output schema, the description carries the burden of explaining results, and it does decode the two levels of state plus outcome and message. It stops short of describing the overall response shape (e.g., whether an items array or counts are returned), which leaves a small gap for a tool an agent will poll.

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 description coverage is 100%, so batchId and waitSeconds are already documented with the same meaning the description repeats (including the 0–50 bound). The description adds no format or edge-case detail for the parameters themselves; its added meaning is about returned states rather than inputs.

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: 'Check a batch of deletions, by its id'. It explicitly disambiguates the two sources of a batch id (request_deletions or a held delete call's return), which separates it from the sibling that creates deletions.

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?

Clear about the context of use — poll this after request_deletions or after a held delete call returns — and tells the agent to pass waitSeconds while the batch is pending or running. No explicit when-not-to-use or alternative is offered, but for a status-polling tool there is little ambiguity left.

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