datalens_collections_deleteDelete a DataLens collection with all nested collections, workbooks, and entries in one call. Use to remove a collection and its entire contents.
Delete a collection with everything it holds: nested collections, workbooks, entries.
| Name | Required | Description | Default |
|---|---|---|---|
| collection_id | Yes | Collection id. |
Changes observed during successful MCP inspections.
v0.122.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already flag destructiveHint=true, but the description adds real value by disclosing the recursive blast radius: nested collections, workbooks and entries are all removed. It stops short of stating irreversibility, required permissions, or whether locked entries block deletion.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, front-loaded with the action and immediately followed by the destructive scope. No filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive single-parameter tool with full annotation coverage and no output schema, the description supplies the key missing behavioral fact (cascade). It omits permissions and irreversibility, but nothing essential to correct invocation is absent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the description adds no syntax or format detail for collection_id beyond what the schema states. Baseline 3 applies for a single fully-documented parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (delete) and resource (collection) and adds the cascade scope ('everything it holds: nested collections, workbooks, entries'). It does not name or contrast with the close sibling datalens_collections_delete_bulk, so an agent must infer the distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no exclusions, and no reference to alternatives such as datalens_collections_delete_bulk for multi-collection deletion or datalens_workbooks_delete for removing a workbook alone. Usage is only implied by the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.