canvases_delete
Delete a canvas by providing its ID. Removes the specified canvas from Slack.
Instructions
Delete a canvas.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| canvas_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Delete a canvas by providing its ID. Removes the specified canvas from Slack.
Delete a canvas.
| Name | Required | Description | Default |
|---|---|---|---|
| canvas_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description lacks any behavioral details such as irreversibility, permission requirements, or impact on related resources. A delete operation requires such disclosure.
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 extremely concise (3 words) and front-loaded. However, it sacrifices necessary detail, earning a 4 rather than 5 due to under-specification.
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?
Despite having one parameter and an output schema (not shown), the description provides no information about return values or side effects. For a delete operation, more context is needed.
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 0%. The description does not explain the canvas_id parameter, its format, or how to obtain it. The parameter is merely listed in the schema with no additional context.
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 clearly states the verb 'Delete' and the resource 'canvas', distinguishing it from sibling tools like canvases_create, canvases_edit, and canvases_access_delete.
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 provided on when to use this tool versus alternatives. There is no mention of prerequisites, side effects, or scenarios where deletion is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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