Create a Slack list in a specific channel, optionally adding initial items. Requires a paid Slack plan and lists:write permission.
Create a new Slack List in a channel. Requires lists:write scope and a paid Slack plan.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | List name | |
| items | No | Optional initial list items (each is a dict with key-value pairs) | |
| channel | Yes | Channel ID to create the list in |
Changes observed during successful MCP inspections.
v0.1.8Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears the behavioral burden. It discloses auth requirements and plan restrictions, which is valuable, but says nothing about response format, side effects beyond creation, or error behavior. Adequate but not rich.
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?
Two short sentences, front-loaded with the core action, followed by the most important requirement. 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 simple 3-parameter create tool, the description covers purpose and prerequisites; the schema handles parameter details. It does not describe return output, and the absence of an output schema means that is a minor gap, but the tool can be invoked correctly with the given information.
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%, so parameters are fully documented there. The description only adds 'in a channel,' which echoes the channel parameter and provides no new semantic value.
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?
Describes a specific action ('Create a new Slack List in a channel') with the resource and location. However, it does not explicitly contrast with sibling tools like update_list or create_list_item, relying on the verb 'create' and 'new' to differentiate.
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?
States a clear prerequisite (lists:write scope, paid plan) but offers no explicit guidance on when to choose this tool over siblings such as update_list or create_list_item. The usage context is implied rather than spelled out.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.