Skip to main content
Glama

Delete a collection

delete_collection
Destructive

Permanently delete one collection and all of its items. This cannot be undone, and confirm must be true.

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": {
      "collection_id": "<collection_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYestrue, confirming the deletion, which cannot be undone.
collection_idYes

Output Schema

NameRequiredDescriptionDefault
deletedYes
items_deletedYes
license_records_deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so safety is covered. The description adds real value beyond that: it discloses the cascade ('all of its items') and irreversibility ('cannot be undone'), which annotations do not convey.

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 short sentences, front-loaded with the effect and followed by the irreversibility/confirm constraint. No filler.

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 two-parameter tool with an output schema and annotations, the essentials are present: what is destroyed, that it is permanent, and the confirm gate. Minor gap is the undocumented collection_id semantics.

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 only 50%: confirm is fully documented by the schema (const:true with its own description), while collection_id has no description anywhere. The description's 'one collection' hints at a single-ID parameter but adds no format, existence, or failure semantics to compensate for the gap.

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 ('Permanently delete one collection') plus the scope of what is removed ('and all of its items'). It is clearly distinguishable from sibling mutations like remove_from_collection, though it does not name a sibling explicitly.

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?

No guidance on when to use this instead of remove_from_collection or update_collection, and no prerequisites beyond the confirm flag. An agent must infer the choice from the names alone.

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