Skip to main content
Glama
karbassi

slack-mcp

by karbassi

canvases_edit

Edit a Slack canvas by providing the canvas ID and an array of changes, where each change is an object with string key-value pairs.

Instructions

Edit a canvas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
canvas_idYes
changesYes

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 present, so the description bears full responsibility. It merely states 'Edit a canvas', which implies mutation but provides no details on what changes are applied, whether the operation is destructive, or if permissions are required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (three words), which is under-specification rather than conciseness. It fails to provide necessary context for a tool with two ambiguous parameters.

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

Completeness2/5

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

Despite having an output schema, the description does not hint at what is returned. For a mutation tool with zero schema coverage and no annotations, the description is incomplete and insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the two required parameters: 'canvas_id' or 'changes'. The format and purpose of 'changes' (array of key-value pairs) are entirely unclear, leaving the AI agent with no semantic guidance.

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 uses the specific verb 'Edit' and resource 'canvas', clearly indicating the tool's action. However, it does not elaborate on what aspects of the canvas can be edited, nor does it differentiate from sibling tools like 'canvases_create' or 'canvases_delete', though the verb itself distinguishes it.

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 is provided on when to use this tool versus alternatives, such as when to create, delete, or access canvas settings. The description offers no context or exclusion criteria.

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