Skip to main content
Glama

get_streams

Retrieve live Twitch streams with filters for game, language, and result count to monitor current broadcasts.

Instructions

現在ライブ配信中のストリームを取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gameNoゲーム名でフィルター
languageNo言語でフィルター (例: ja, en)
limitNo取得する最大ストリーム数(デフォルト: 20)

Implementation Reference

  • The handler function that executes the tool logic: fetches live streams filtered by game, language, or limit using Twitch API and maps the response.
    export async function handleGetStreams(
      apiClient: ApiClient,
      args: { game?: string; language?: string; limit?: number }
    ) {
      const streams = await apiClient.streams.getStreams({
        game: args.game,
        language: args.language,
        limit: args.limit,
      });
    
      return formatResponse(
        streams.data.map(stream => ({
          userId: stream.userId,
          userName: stream.userName,
          title: stream.title,
          game: stream.gameName,
          viewers: stream.viewers,
          startedAt: stream.startDate,
          language: stream.language,
          thumbnailUrl: stream.thumbnailUrl,
          tags: stream.tags,
        }))
      );
    }
  • Tool schema definition specifying the name, description, and input schema for get_streams.
      name: 'get_streams',
      description: '現在ライブ配信中のストリームを取得します',
      inputSchema: {
        type: 'object',
        properties: {
          game: {
            type: 'string',
            description: 'ゲーム名でフィルター',
          },
          language: {
            type: 'string',
            description: '言語でフィルター (例: ja, en)',
          },
          limit: {
            type: 'number',
            description: '取得する最大ストリーム数(デフォルト: 20)',
            minimum: 1,
            maximum: 100,
          },
        },
      },
    },
  • src/index.ts:118-123 (registration)
    Registration of the get_streams tool in the main server switch statement, calling the handler with parsed arguments.
    case 'get_streams':
      return await handleGetStreams(this.apiClient, {
        game: args.game as string | undefined,
        language: args.language as string | undefined,
        limit: args.limit as number | undefined
      });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions retrieving 'currently live' streams but doesn't describe return format, pagination behavior, rate limits, authentication requirements, or what happens when no streams match filters. For a read operation with 3 parameters, this leaves significant behavioral gaps.

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 that states the core purpose without unnecessary words. It's appropriately sized for a straightforward retrieval tool and front-loads the essential information about what the tool does.

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?

For a tool with 3 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what data is returned, how results are structured, whether there's pagination, or any error conditions. The agent would need to guess about the response format and behavior despite having clear input parameters.

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 all 3 parameters with descriptions. The tool description adds no additional parameter semantics beyond what's in the schema. This meets the baseline of 3 when schema coverage is high, but doesn't provide extra value like explaining parameter interactions or providing usage examples.

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/retrieve) and resource ('現在ライブ配信中のストリーム' - currently live streaming streams), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'get_stream_info' or 'get_videos', but the focus on 'currently live' provides some implicit distinction.

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 'get_stream_info' (for specific streams), 'get_videos' (for past videos), or 'search_channels' (for channel information). There's no mention of prerequisites, limitations, or comparative use cases with sibling tools.

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