Skip to main content
Glama
karbassi

slack-mcp

by karbassi

slack_lists_items_delete

Remove a specific list item from a Slack list by providing the item ID and list ID.

Instructions

Delete a list item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesID of the list item (record) to delete.
list_idYesID of the list (a file ID) containing the item (e.g. ``F0123``).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided; the description only states 'delete'. For a deletion tool, the description does not disclose irreversibility, permissions, or side effects beyond the basic action.

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?

Extremely concise with a single sentence, no fluff, and directly states the core function.

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?

Given the simple deletion operation, the description is sufficient. The existence of an output schema reduces the need to explain return values. However, it could mention that it deletes exactly one item.

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?

Input schema has 100% description coverage; both parameters are well-documented in the schema. The tool description adds no additional value beyond what is already in the schema.

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?

The description 'Delete a list item' clearly states the action and resource. It is distinct from the sibling 'slack_lists_items_delete_multiple' by implying single-item deletion, though not explicitly stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs alternatives. The context implies it's for deleting a single list item, but there is no mention of prerequisites or exclusions.

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