Skip to main content
Glama
z9905080

MCP Server for Slack

by z9905080

slack_get_user_profile

Retrieve detailed profile information for a specific Slack user by providing their user ID.

Instructions

Get detailed profile information for a specific user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesThe ID of the user

Implementation Reference

  • Core handler function in SlackClient that performs the API call to retrieve detailed user profile information from Slack's users.profile.get endpoint.
    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();
    }
  • Tool dispatch handler in the CallToolRequest that validates arguments and calls the SlackClient.getUserProfile method.
    case "slack_get_user_profile": {
      const args = request.params
        .arguments as unknown as GetUserProfileArgs;
      if (!args.user_id) {
        throw new Error("Missing required argument: user_id");
      }
      const response = await slackClient.getUserProfile(args.user_id);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Tool schema definition including name, description, and input schema for validation.
    const getUserProfileTool: Tool = {
      name: "slack_get_user_profile",
      description: "Get detailed profile information for a specific user",
      inputSchema: {
        type: "object",
        properties: {
          user_id: {
            type: "string",
            description: "The ID of the user",
          },
        },
        required: ["user_id"],
      },
    };
  • index.ts:567-582 (registration)
    Registration of the tool in the ListToolsRequest handler, making it discoverable by clients.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      console.log("Received ListToolsRequest");
      return {
        tools: [
          listChannelsTool,
          postMessageTool,
          replyToThreadTool,
          addReactionTool,
          getChannelHistoryTool,
          getThreadRepliesTool,
          getUsersTool,
          getUserProfileTool,
          lookupUserByEmailTool,
        ],
      };
    });
  • TypeScript interface defining the expected arguments for the tool.
    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 of behavioral disclosure. It states it 'Get[s] detailed profile information', which implies a read-only operation, but doesn't specify authentication needs, rate limits, error conditions, or what 'detailed' entails (e.g., fields returned). This is a significant gap for a tool with zero annotation coverage.

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, efficient sentence with zero waste—it directly states the tool's purpose without redundancy. It's appropriately sized for a simple retrieval tool and front-loaded with the core action.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what 'detailed profile information' includes (e.g., fields like email, status, timezone), how errors are handled, or any behavioral traits. For a tool with rich potential output, this leaves critical gaps for an agent.

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%, with the single parameter 'user_id' documented in the schema as 'The ID of the user'. The description adds no additional meaning beyond this, as it doesn't explain format (e.g., Slack user ID syntax) or provide examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Get' and the resource 'detailed profile information for a specific user', making the purpose unambiguous. It doesn't explicitly distinguish from siblings like 'slack_get_users' (which likely lists multiple users), but the specificity of 'for a specific user' implies a single-user focus.

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 like 'lookup_user_by_email' or 'slack_get_users'. It mentions 'for a specific user' but doesn't clarify prerequisites (e.g., needing a user ID) or exclusions, leaving usage context implied rather than explicit.

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

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