Skip to main content
Glama
karbassi

slack-mcp

by karbassi

usergroups_create

Create a Slack user group with a unique name and optional default channels, description, mention handle, and other settings.

Instructions

Create a User Group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesA name for the User Group (must be unique among User Groups).
handleNoA mention handle (must be unique among channels, users, and User Groups).
team_idNoEncoded team ID where the User Group exists, required if org token is used (e.g. ``T0123``).
channelsNoComma-separated string of default channel IDs for the User Group (e.g. ``C0123,C0456``).
descriptionNoA short description of the User Group.
include_countNoInclude the number of users in each User Group in the response.
enable_sectionNoWhether to enable a section for the User Group.
additional_channelsNoComma-separated additional default channel IDs to add beyond ``channels`` (e.g. ``C0789``).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

With no annotations, the description must disclose behavioral traits, but it only states 'Create a User Group.' No information about side effects, error conditions, or required permissions.

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

Conciseness1/5

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

The description is only four words, which is too brief for a tool with 8 parameters and no annotations. It lacks essential details and is under-informative.

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

Completeness1/5

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

Given the complexity (8 params, output schema exists), the description is incomplete. It fails to explain the output, typical usage, or what happens on success/failure.

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%, so the schema already describes all parameters. The description adds no extra meaning beyond the schema, resulting in baseline score for high coverage.

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 verb 'Create' with the resource 'User Group', clearly indicating the action. It distinguishes from siblings like usergroups_enable or usergroups_list, which are different operations.

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 mentioned, and no context about required permissions or typical use cases.

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