Skip to main content
Glama

search_categories

Find Twitch game categories using search keywords to organize streams and content discovery.

Instructions

ゲームやカテゴリーを検索します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes検索キーワード
limitNo取得する最大カテゴリー数(デフォルト: 20)

Implementation Reference

  • The handler function that performs the search for categories using the Twitch API client and returns formatted results.
    export async function handleSearchCategories(
      apiClient: ApiClient,
      args: { query: string; limit?: number }
    ) {
      const categories = await apiClient.search.searchCategories(args.query, { limit: args.limit });
    
      return formatResponse(
        categories.data.map(category => ({
          id: category.id,
          name: category.name,
          boxArtUrl: category.boxArtUrl,
        }))
      );
    }
  • The input schema definition for the search_categories tool, specifying required query parameter and optional limit.
    {
      name: 'search_categories',
      description: 'ゲームやカテゴリーを検索します',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: '検索キーワード',
          },
          limit: {
            type: 'number',
            description: '取得する最大カテゴリー数(デフォルト: 20)',
            minimum: 1,
            maximum: 100,
          },
        },
        required: ['query'],
      },
    },
  • src/index.ts:106-110 (registration)
    The switch case in the main server request handler that routes calls to the search_categories tool to its handler function.
    case 'search_categories':
      return await handleSearchCategories(this.apiClient, {
        query: args.query as string,
        limit: args.limit as number | undefined
      });
  • src/index.ts:17-17 (registration)
    Import statement that brings in the handleSearchCategories handler function for use in the server.
    import { handleGetTopGames, handleGetGame, handleSearchCategories } from './tools/handlers/game.js';
Behavior1/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 tool searches, with no information on permissions, rate limits, pagination, or what the response looks like (e.g., format, fields). This is inadequate for a search 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 in Japanese ('ゲームやカテゴリーを検索します'), which translates to 'Searches for games or categories.' It's front-loaded with the core action and resource, with zero wasted words, making it highly concise and well-structured.

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, no output schema, and a search tool with two parameters, the description is incomplete. It lacks details on behavioral traits, return values, and usage context, making it insufficient for an agent to understand how to effectively invoke this tool beyond basic parameter input.

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%, so the schema already documents both parameters ('query' and 'limit') with descriptions and constraints. The description adds no additional meaning beyond what the schema provides, such as examples or context for the search query. 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.

Purpose3/5

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

The description states the tool searches for 'games or categories' which gives a general purpose, but it's vague about what exactly is being searched (e.g., Twitch categories) and doesn't distinguish it from sibling tools like 'search_channels' or 'get_top_games'. It provides a verb ('search') and resource ('games/categories') but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives like 'search_channels' or 'get_top_games'. The description implies usage for searching but doesn't specify context, exclusions, or prerequisites, leaving the agent to guess based on tool names alone.

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