Skip to main content
Glama

get_channel_info

Retrieve detailed Twitch channel information including stream status, viewer count, and broadcaster details to monitor or analyze channel performance.

Instructions

チャンネル情報を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelNameYesTwitchチャンネル名

Implementation Reference

  • The handler function that implements the core logic of the get_channel_info tool, fetching user and channel information from Twitch API.
    export async function handleGetChannelInfo(apiClient: ApiClient, args: { channelName: string }) {
      const user = await getUserByName(apiClient, args.channelName);
      const channel = await apiClient.channels.getChannelInfoById(user.id);
    
      const response: any = {
        id: user.id,
        name: user.name,
        displayName: user.displayName,
        description: user.description,
        profilePictureUrl: user.profilePictureUrl,
        creationDate: user.creationDate,
      };
    
      if (channel) {
        response.channel = {
          name: channel.name,
          game: channel.gameName,
          title: channel.title,
          language: channel.language,
          tags: channel.tags,
        };
      }
    
      return formatResponse(response);
    }
  • The input schema and metadata definition for the get_channel_info tool.
    {
      name: 'get_channel_info',
      description: 'チャンネル情報を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          channelName: {
            type: 'string',
            description: 'Twitchチャンネル名',
          },
        },
        required: ['channelName'],
      },
    },
  • src/index.ts:86-89 (registration)
    Registration and dispatch of the get_channel_info tool handler in the MCP server's CallToolRequestSchema handler.
    case 'get_channel_info':
      return await handleGetChannelInfo(this.apiClient, {
        channelName: args.channelName as string
      });
  • src/index.ts:15-15 (registration)
    Import of the get_channel_info handler function.
    import { handleGetChannelInfo, handleGetChatSettings } from './tools/handlers/channel.js';
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action ('取得します' - get/retrieve) without mentioning whether this is a read-only operation, requires authentication, has rate limits, or what the return format might be. For a tool with zero annotation coverage, 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.

Conciseness5/5

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

The description is extremely concise - a single Japanese sentence that directly states the tool's function. There's no wasted language or unnecessary elaboration. It's appropriately sized for a simple retrieval tool.

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 'channel information' includes (profile data, statistics, etc.) or the response format. For a tool in a Twitch API context with multiple similar siblings, more context is needed to distinguish its specific purpose.

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 single parameter 'channelName' clearly documented as 'Twitchチャンネル名' (Twitch channel name). The description doesn't add any parameter details beyond what the schema provides, so it meets the baseline of 3 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.

Purpose2/5

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

The description 'チャンネル情報を取得します' (Get channel information) states the basic action but is vague about what 'channel information' includes. It doesn't distinguish this tool from siblings like get_stream_info or get_users, which also retrieve channel-related data. While it identifies the resource (channel), it lacks specificity about what information is retrieved.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 siblings like get_stream_info (for stream status) and get_users (for user data), there's no indication of when this specific channel info tool is appropriate. No context, exclusions, or alternatives are mentioned.

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