Skip to main content
Glama
karbassi

slack-mcp

by karbassi

users_set_photo

Update your Slack profile photo by providing a base64-encoded image. Optionally specify crop dimensions to adjust the image.

Instructions

Set the user profile photo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
crop_wNoWidth/height of the square crop box, in pixels (the crop is always square).
crop_xNoX coordinate of the top-left corner of the crop box, in pixels.
crop_yNoY coordinate of the top-left corner of the crop box, in pixels.
image_base64YesThe image to set, as a base64-encoded string of the raw image bytes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided. The description does not disclose behavioral traits such as whether the photo is replaced, size constraints, authorization requirements, or error handling. For a mutation tool, this is insufficient.

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

Conciseness4/5

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

Description is a single concise sentence with no waste. However, it could benefit from a slightly more structured explanation of the operation.

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?

Output schema exists, so return values are covered. The tool is relatively simple, but missing context like 'sets the photo for the authenticated user' or that it replaces the existing photo.

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 parameters are well-documented in the schema. The description adds no additional meaning; baseline of 3 is appropriate.

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?

Description clearly states 'Set the user profile photo' with a specific verb and resource. It distinguishes from sibling 'users_delete_photo' and 'users_profile_set', but doesn't specify which user's photo is being set (implied authenticated user).

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 like 'users_profile_set' or 'users_delete_photo'. No prerequisites or context 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