Skip to main content
Glama
zencoderai

Slack

by zencoderai

Get Slack User Profile

slack_get_user_profile

Retrieve detailed profile information for a specific Slack user by providing their user ID. Essential for accessing user details like name, email, and role within a workspace.

Instructions

Get detailed profile information for a specific user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesThe ID of the user

Implementation Reference

  • index.ts:358-373 (registration)
    Registration of the slack_get_user_profile tool using server.registerTool with input schema and handler callback.
    server.registerTool(
      "slack_get_user_profile",
      {
        title: "Get Slack User Profile",
        description: "Get detailed profile information for a specific user",
        inputSchema: {
          user_id: z.string().describe("The ID of the user"),
        },
      },
      async ({ user_id }) => {
        const response = await slackClient.getUserProfile(user_id);
        return {
          content: [{ type: "text", text: JSON.stringify(response) }],
        };
      }
    );
  • The SlackClient.getUserProfile method that executes the tool logic by calling Slack's users.profile.get API with the user_id parameter.
    async getUserProfile(user_id: string): Promise<any> {
      const params = new URLSearchParams({
        user: user_id,
        include_labels: "true",
      });
    
      const response = await fetch(
        `https://slack.com/api/users.profile.get?${params}`,
        { headers: this.botHeaders },
      );
    
      return response.json();
    }
  • TypeScript interface defining the input arguments for getUserProfile (user_id string).
    interface GetUserProfileArgs {
      user_id: string;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden but only states the purpose, not behavioral details like permissions, rate limits, or side effects.

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?

The description is a single sentence that is concise and front-loaded, with no wasted words.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description is adequate but lacks details about return format or error conditions.

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 description coverage is 100%, and the description adds no extra meaning beyond what the schema already provides for the single parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get') and the resource ('detailed profile information for a specific user'), and it is distinct from siblings like slack_get_users which lists users.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions.

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/zencoderai/slack-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server