Skip to main content
Glama
karbassi

slack-mcp

by karbassi

slack_lists_items_delete_multiple

Delete multiple items from a Slack list by providing the list ID and item IDs.

Instructions

Delete multiple list items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesID of the list (a file ID) containing the items (e.g. ``F0123``).
item_idsYesIDs of the list items (records) to delete.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, and the description only states 'Delete multiple list items.' It fails to disclose any behavioral traits such as required permissions, whether deletion is reversible, or what happens if some items fail to delete. The description carries the full burden here and is insufficient.

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?

The description is a single, concise sentence with no redundant words. It conveys the core action efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists (though not provided in detail), the description does not need to explain return values. However, for a deletion tool, it lacks information about success/failure behavior, idempotency, or potential side effects. It is minimally adequate but could be more complete.

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 100% with descriptions for list_id and item_ids. The description adds no additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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?

Description is 'Delete multiple list items.' which is a specific verb+resource pair. It clearly indicates multiple deletion, distinguishing it from sibling tools like slack_lists_items_delete (single deletion).

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 tool versus alternatives. Although siblings exist (e.g., slack_lists_items_delete for single items), the description does not mention them or provide any context for decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/karbassi/slack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server