Skip to main content
Glama

get_users

Retrieve detailed Twitch user information by providing usernames, enabling profile lookups and data access for channel management.

Instructions

ユーザーの情報を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNamesYesTwitchユーザー名の配列

Implementation Reference

  • The main handler function for the 'get_users' tool. Fetches users by names using Twitch API and returns formatted user details including id, name, display name, etc.
    export async function handleGetUsers(apiClient: ApiClient, args: { userNames: string[] }) {
      const users = await apiClient.users.getUsersByNames(args.userNames);
    
      return formatResponse(
        users.map(user => ({
          id: user.id,
          name: user.name,
          displayName: user.displayName,
          description: user.description,
          profilePictureUrl: user.profilePictureUrl,
          offlinePlaceholderUrl: user.offlinePlaceholderUrl,
          creationDate: user.creationDate,
          broadcasterType: user.broadcasterType,
          type: user.type,
        }))
      );
    }
  • Schema definition for the 'get_users' tool, specifying input as an object with required 'userNames' array of strings (max 100).
    {
      name: 'get_users',
      description: 'ユーザーの情報を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          userNames: {
            type: 'array',
            description: 'Twitchユーザー名の配列',
            items: {
              type: 'string',
            },
            maxItems: 100,
          },
        },
        required: ['userNames'],
      },
    },
  • src/index.ts:131-134 (registration)
    Registration of the 'get_users' tool handler in the switch statement for CallToolRequestSchema, dispatching to handleGetUsers with parsed arguments.
    case 'get_users':
      return await handleGetUsers(this.apiClient, {
        userNames: args.userNames as string[]
      });
  • src/index.ts:20-20 (registration)
    Import statement registering the handleGetUsers function for use in the tool dispatcher.
    import { handleGetUsers } from './tools/handlers/user.js';
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action ('get user information') without mentioning permissions, rate limits, response format, or any constraints (e.g., the 100-item max from the schema). This leaves significant gaps in understanding the tool's behavior.

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?

The description is a single, efficient sentence in Japanese that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, though it could be more informative without sacrificing conciseness.

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 the tool's complexity (a read operation with one parameter) and lack of annotations and output schema, the description is incomplete. It does not explain what user information is returned, any limitations, or how it fits with siblings, making it inadequate for full contextual understanding.

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?

The schema description coverage is 100%, with the parameter 'userNames' well-documented in the schema as 'Twitchユーザー名の配列' (array of Twitch usernames) with a maxItems of 100. The description adds no additional meaning beyond this, so it meets the baseline of 3 where the schema does the heavy lifting.

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

Purpose3/5

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

The description 'ユーザーの情報を取得します' (Get user information) states the basic purpose with a clear verb ('取得します' - get) and resource ('ユーザーの情報' - user information). However, it lacks specificity about what type of user information or how it differs from sibling tools like 'get_channel_info' or 'search_channels', making it somewhat vague rather than precisely distinguished.

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. With sibling tools like 'get_channel_info' and 'search_channels' that might overlap in user-related queries, there is no indication of context, prerequisites, or exclusions, leaving the agent without usage direction.

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/mtane0412/twitch-mcp-server'

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