Bulk-delete selected items from a Skylight list by supplying the list ID and the item IDs to remove.
Bulk-delete specific list items.
| Name | Required | Description | Default |
|---|---|---|---|
| listId | Yes | ||
| frameId | No | ||
| item_ids | Yes | List-item ids to delete. |
Changes observed during successful MCP inspections.
v1.0.1Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"v0.7.1Input schema / properties / item_ids / items / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "number"
- }
-]Input schema / properties / item_ids / items / typeAdded value: +[
+ "string",
+ "number"
+]v0.4.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds the useful scope that only specified items are deleted, not the entire list, but it does not disclose additional behavioral traits such as irreversibility or side effects. No contradiction with annotations.
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?
The description is a single efficient sentence with no filler, front-loading the action ('Bulk-delete') and the target resource ('specific list items').
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 3-parameter operation with no output schema, the description omits required-parameter context, optional frameId semantics, and differentiation from sibling deletion tools. Annotations cover the destructive nature, but not enough guidance for a fully informed call.
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 only 33%, and the description adds no parameter meaning beyond what the schema contains. item_ids is already described, while listId and frameId remain unexplained; frameId in particular is ambiguous.
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?
The description states a clear verb and resource: 'Bulk-delete specific list items.' This distinguishes it from the singular skylight_delete_list_item and from clearing an entire list, though it could more explicitly name the scope as 'items within the given listId'.
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 guidance is given on when to use this tool versus skylight_delete_list_item, skylight_clear_list, or other list-item operations. The word 'bulk' implies multiple items, but no explicit context or alternatives are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.