datalens_collections_delete_bulkDelete multiple collections and all their contents at once by providing collection IDs. Use for bulk cleanup of DataLens collections.
Delete several collections with everything they hold.
| Name | Required | Description | Default |
|---|---|---|---|
| collection_ids | Yes | Collection ids. |
Changes observed during successful MCP inspections.
v0.122.1Does 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 structurally. The description adds real value by disclosing the cascade semantics ('with everything they hold'), which the annotations do not convey. It stops short of stating irreversibility or partial-failure behavior.
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?
A single sentence, front-loaded with the verb and the cascade warning, with no wasted words. It is efficient for a one-parameter tool, though extremely terse.
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 simple one-parameter bulk delete with no output schema and annotations that already carry the destructive/idempotency profile, the description plus structured fields are sufficient to invoke it. The cascade note is the key missing-from-schema detail and it is present.
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% for the single parameter, so the schema already documents collection_ids as an array of ids. The description adds nothing beyond what the schema provides, making the baseline 3 appropriate.
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+resource ('Delete ... collections') with a clear scope worth ('several') and effect ('with everything they hold'). The 'several/bulk' framing implicitly separates it from the singular datalens_collections_delete sibling, though no sibling is named explicitly.
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?
The description gives no when-to-use guidance, no condition that selects bulk deletion over single deletion, and no prerequisites such as required permissions or confirmation. It only restates the action.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.