Skip to main content
Glama

get_clips

Retrieve Twitch clips from specific channels to analyze content performance or gather highlights for review and sharing.

Instructions

クリップの情報を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelNameYesTwitchチャンネル名
limitNo取得する最大クリップ数(デフォルト: 20)

Implementation Reference

  • The handler function that fetches clips for the specified channel using Twitch API, resolves the broadcaster ID, retrieves clips, maps them to a simplified format, and returns formatted response.
    export async function handleGetClips(
      apiClient: ApiClient,
      args: { channelName: string; limit?: number }
    ) {
      const user = await getUserByName(apiClient, args.channelName);
      const clips = await apiClient.clips.getClipsForBroadcaster(user.id, { limit: args.limit });
    
      return formatResponse(
        clips.data.map(clip => ({
          id: clip.id,
          url: clip.url,
          embedUrl: clip.embedUrl,
          broadcasterId: clip.broadcasterId,
          broadcasterName: clip.broadcasterDisplayName,
          creatorId: clip.creatorId,
          creatorName: clip.creatorDisplayName,
          videoId: clip.videoId,
          gameId: clip.gameId,
          language: clip.language,
          title: clip.title,
          viewCount: clip.views,
          creationDate: clip.creationDate,
          thumbnailUrl: clip.thumbnailUrl,
          duration: clip.duration,
        }))
      );
    }
  • Tool definition including name, description, and input schema for validating arguments: channelName (required) and optional limit.
    {
      name: 'get_clips',
      description: 'クリップの情報を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          channelName: {
            type: 'string',
            description: 'Twitchチャンネル名',
          },
          limit: {
            type: 'number',
            description: '取得する最大クリップ数(デフォルト: 20)',
            minimum: 1,
            maximum: 100,
          },
        },
        required: ['channelName'],
      },
    },
  • src/index.ts:136-140 (registration)
    Registration in the MCP server's CallToolRequestSchema handler switch statement, dispatching 'get_clips' calls to the handleGetClips function.
    case 'get_clips':
      return await handleGetClips(this.apiClient, {
        channelName: args.channelName as string,
        limit: args.limit as number | undefined
      });
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 ('get clip information') without detailing traits like whether it's read-only (implied but not explicit), rate limits, authentication needs, error handling, or what the return format might be. For a tool with no annotation coverage, this is a significant gap in transparency.

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, concise sentence ('クリップの情報を取得します') that directly states the tool's purpose without any fluff or redundancy. It is front-loaded and efficiently communicates the core action, making it easy to parse quickly.

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 complexity (a read operation with 2 parameters) and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'clip information' entails, how results are returned (e.g., list format, pagination), or any behavioral aspects. For a tool without structured output or annotations, more context is needed to guide effective use.

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 clear descriptions for both parameters (channelName and limit). The description adds no additional meaning beyond what the schema provides, such as explaining parameter interactions or usage examples. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema adequately documents the parameters.

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 purpose ('クリップの情報を取得します' translates to 'Get clip information'), which is clear but vague. It specifies the resource (clips) and verb (get), but doesn't distinguish it from potential siblings like get_videos or get_streams, nor does it specify what kind of clip information (e.g., metadata, URLs, statistics). This makes it adequate but with room for improvement.

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 context (e.g., for Twitch clips), prerequisites, or exclusions, leaving the agent to infer usage from the tool name and schema alone. This lack of explicit guidance reduces its effectiveness in tool selection.

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