Skip to main content
Glama

search_channels

Find Twitch channels by name or keyword to discover streamers and content matching your interests.

Instructions

チャンネルを検索します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes検索キーワード
limitNo取得する最大チャンネル数(デフォルト: 20)

Implementation Reference

  • The handler function that executes the search_channels tool logic by querying the Twitch API for channels matching the search query and formatting the results.
    export async function handleSearchChannels(
      apiClient: ApiClient,
      args: { query: string; limit?: number }
    ) {
      const channels = await apiClient.search.searchChannels(args.query, { limit: args.limit });
    
      return formatResponse(
        channels.data.map(channel => ({
          id: channel.id,
          name: channel.name,
          displayName: channel.displayName,
          game: channel.gameName,
          language: channel.language,
          tags: channel.tags,
        }))
      );
    }
  • src/index.ts:112-116 (registration)
    Registers and dispatches the search_channels tool by calling the handleSearchChannels handler in the MCP server request handler.
    case 'search_channels':
      return await handleSearchChannels(this.apiClient, {
        query: args.query as string,
        limit: args.limit as number | undefined
      });
  • Defines the tool metadata including name, description, and input schema (query string required, optional limit) for search_channels.
    name: 'search_channels',
    description: 'チャンネルを検索します',
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: '検索キーワード',
        },
        limit: {
          type: 'number',
          description: '取得する最大チャンネル数(デフォルト: 20)',
          minimum: 1,
          maximum: 100,
        },
      },
      required: ['query'],
    },
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 action ('search') without details on permissions, rate limits, response format, or any side effects. For a search tool with no annotations, this is inadequate as it leaves key behavioral traits unspecified.

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 in Japanese ('チャンネルを検索します'), which is appropriately sized and front-loaded with the core action. There is no wasted text, making it highly concise and well-structured for its purpose.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the search returns (e.g., channel details, lists), how results are filtered, or any limitations. For a tool with 2 parameters and no structured output info, the description should provide more context to guide usage effectively.

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 input schema has 100% description coverage, with clear documentation for 'query' and 'limit'. The description adds no additional meaning beyond what the schema provides, such as examples or context for parameter usage. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema handles 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 'チャンネルを検索します' (Search for channels) clearly states the verb ('search') and resource ('channels'), making the basic purpose understandable. However, it doesn't differentiate this tool from sibling tools like 'search_categories' or 'get_streams', which might also involve channel-related operations. The purpose is stated but lacks specificity about what makes this search unique.

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. It doesn't mention any context, prerequisites, or exclusions, such as how it differs from 'get_streams' or 'search_categories'. Without this, an agent might struggle to choose the right tool among siblings.

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