Crawlora MCP

twitch_clips

Read-only

Fetch a Twitch channel's clips from the last seven days, ranked by views. Use twitch_videos for past broadcasts, twitch_streams for live streams, or twitch_channel for channel details.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "login": "<login>"
    },
    "name": "twitch_clips"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of clips to return (default 20, max 100)
`login`	Yes	Twitch channel login (the lowercase URL slug, e.g. caedrel for twitch.tv/caedrel)

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / limit / description

Added value: +"Number of clips to return (default 20, max 100)"

addedInput schema / properties / login / description

Added value: +"Twitch channel login (the lowercase URL slug, e.g. caedrel for twitch.tv/caedrel)"

First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine behavioral context beyond that: the seven-day recency window and view-based ranking, which shape what results to expect. It stops short of describing pagination or result shape, but the output schema carries that.

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?

Two sentences, zero waste. The core scope (seven days, ranked by views) is front-loaded, and the sibling routing follows immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with an output schema and full annotation coverage, the description supplies everything needed: what it returns, its recency constraint, and how it differs from the other Twitch tools. Nothing an agent needs to call it correctly is missing.

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 coverage is 100%, and both parameters (login, limit) are fully documented in the schema itself, so the baseline is 3. The description adds only the implicit 'ranked by views' ordering hint, no format or syntax detail beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

States a specific verb (Fetch) and resource (a Twitch channel's clips) with clear scope modifiers (last seven days, ranked by views). It explicitly distinguishes itself from sibling tools by naming twitch_videos, twitch_streams, and twitch_channel as the right tools for other resource types.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names three alternatives and the exact condition that selects each: past broadcasts, live streams, channel details. An agent can route confidently without opening any other schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?