Skip to main content
Glama
karbassi

slack-mcp

by karbassi

workflows_update_step

Update a workflow step's configuration, including inputs, outputs, name, and image, using the step edit ID from a view submission.

Instructions

Update the configuration for a workflow step.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputsNoKey-value map of inputs from the user's step configuration; each value has a ``value`` property.
outputsNoA list of output objects (each with ``name``, ``type``, and ``label``) used during step execution.
step_nameNoOptional override for the name shown to users in the Workflow Builder for this step.
step_image_urlNoOptional override for the image shown to users in the Workflow Builder for this step.
workflow_step_edit_idYesA context identifier from the ``view_submission`` payload, mapping to editing a step.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description carries full burden but only says 'Update'. It does not disclose mutation behavior, authorization needs, reversibility, or error conditions.

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?

Single sentence, no fluff, efficient for its purpose.

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?

Has output schema (implied) and full parameter descriptions, but lacks context on constraints like editing ID validity or step existence.

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 individual parameter descriptions, so baseline 3. The tool description adds no extra meaning beyond 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 clearly states the verb 'Update' and the resource 'configuration for a workflow step'. It distinguishes from sibling tools like workflows_step_completed or workflows_step_failed which handle different actions.

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. No prerequisites, context, or exclusion criteria provided.

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